opted.
There's nothing in your proposal that is outside of your control,
as far as I can tell.
(Well, except for easy_install not being in the stdlib, but that's
no barrier to adoption of the proposed tool.)
--
R. David Murray www.bitdance.com
_
On Tue, 27 Jul 2010 13:11:48 +0200, Georg Brandl wrote:
> Am 27.07.2010 10:54, schrieb David:
> > I'd welcome any patch submitted to Rietveld for review. However, your
> > proposed "review.py" module does not exist as far as I know, and unless
>
ntly added the old re cache-clearing strategy to
fnmatch, because previously its cache would grow indefinitely.
It sounds like this should be applied there as well.
That's three...time to figure out how to share the code?
--
R. David Murray www.bitdance.c
ific.
Anyone who cares about config file locations should read issue 7175.
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Uns
ds, titles, and URL. Ezio just
finished reworking the summary script to be more easily modified, so I
bet he would find this easy to add at this point.
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/p
27;t see a downside to
that. Most unix applications look in multiple places for configuration
info.
Michael seems to be arguing for not using the standard OSX locations
because the Finder can't edit them anyway. Is that true?
--
R. David Murray w
t;
> +tests = list(tests)
I guess you didn't notice that just above this code is a clause that
says 'if forever' which implements -F/--forever by making tests into a
generator that never runs out...
--
R. David Murray
On Mon, 02 Aug 2010 21:51:11 -0400, "R. David Murray"
wrote:
> On Mon, 02 Aug 2010 20:59:52 +0200, georg.brandl
> wrote:
> > Author: georg.brandl
> > Date: Mon Aug 2 20:59:52 2010
> > New Revision: 83543
Hmm. Looking at the format of this message as it c
x27;t exist.
Fixed. Apparently a line was dropped when applying a patch to
the tracker, but the mistake didn't surface until roundup
was restarted after the reboot.
--
R. David Murray www.bitdance.com
___
Python-
Am I missing something, or this a missing feature?
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.py
On Tue, 03 Aug 2010 12:22:30 -0500, Benjamin Peterson
wrote:
> 2010/8/3 R. David Murray :
> > So I thought I'd break the exception chain before raising the error the
> > test harness really wants to raise. However, I can't figure out any way
> > to do that. Am
On Tue, 03 Aug 2010 20:36:36 +0200, Georg Brandl wrote:
> Am 03.08.2010 19:05, schrieb Brian Curtin:
> > On Tue, Aug 3, 2010 at 11:58, R. David Murray
> > Fixed. Apparently a line was dropped when applying a patch to
> > the tracker, but the mistake didn&#x
Hmm. If we added a 'binsearch' option to regrtest, you could just
pass it the random seed and that option and off it would go...
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@pyt
eek. He's going to fix
that.
> > Issues closed (154)
> > ===
> >
> > #1474680: pickling files works with protocol=2.
> > http://bugs.python.org/issue1474680 closed by alexandre.vassalotti
> > [...]
>
> This is the list of *all* the is
On Mon, 23 Aug 2010 15:13:34 +0100, Mark Lawrence
wrote:
> Suffering from dead parrot syndrome? Kiss of life please :)
The hosting company has been notified.
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mail
x27;re in an old-style class, you shouldn't get an double
> underscore methods in __getattr__ (or __getattribute__). If you do,
> it's a bug.
Benjamin, I remember you fixing various special method lookups, so just
for clarity's sake, which versions of Python d
yourself there.
All help is welcome! It is not a "porting" project strictly
speaking, but it certainly is interesting :)
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
h
stand working on my client in Python2, I wanted to be using Python3.
So I volunteered to help with email...but I figure I'll come back around
and help Antoine with nttplib by and by :)
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
ing strings.
It also has to use slice notation rather than indexing when looking at
individual characters, which is a PITA but not terrible.
I'm not saying this is the best approach, since this is all experimental
code at the moment, but it is *an* approach
--
R. David Murray
On Thu, 16 Sep 2010 17:40:53 +0200, Antoine Pitrou wrote:
> On Thu, 16 Sep 2010 11:30:12 -0400
> "R. David Murray" wrote:
> >
> > And then BaseHeader uses self.lit.colon, etc, when manipulating strings.
> > It also has to use slice notation rather than index
On Thu, 16 Sep 2010 18:11:30 -0400, Glyph Lefkowitz
wrote:
> On Sep 16, 2010, at 4:51 PM, R. David Murray wrote:
>
> > Given a message, there are many times you want to serialize it as text
> > (for example, for presentation in a UI). You could provide alternate
> >
On Fri, 17 Sep 2010 00:05:12 +0200, Antoine Pitrou wrote:
> On Thu, 16 Sep 2010 16:51:58 -0400
> "R. David Murray" wrote:
> >
> > What do we store in the model? We could say that the model is always
> > text. But then we lose information about the origin
thon-dev. But the email-sig has put in a lot of
> work on specific API and implementation designs for the email package, so any
> deviation really needs to be debated, discussed, and decided there.
I am also finding it useful to have the API exposed to a wider audience
for f
also slated to be a back-end API for storing parts of messages
elsewhere than in memory, though I haven't worked out what that is going
to look like yet.
But we are definitely getting off topic now :)
--David
___
Python-Dev mailing list
Python-Dev@p
ontent* of head, body, article, post, and ihave commands
is bytes, otherwise you are dealing with strings. I think it is a
very clear and obvious distinction, myself.
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mai
rett reduces that operating consensus
to a written document things will be clearer.
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
opinion on that aspect of it.
For me the change is about making it easier for the dev community
(who are using/creating the development infrastructure) to update the
relevant documentation.
--
R. David Murray www.bitdance.com
___
the convenience to the developers of having them in the source tree.
A separate repository would also be fine, IMO. If someone can find or
write the code to publish that repository to the appropriate location
automatically, we could presumably do this even before the rest of the
hg transit
h of somebodies who *do* care, then the wiki
would be much more useful. But I still don't want to edit the
dev docs there, if I have a choice :) There's a reason I stopped
updating the wiki as soon as I moved to a code repository.
--
R. David Murray
es
was causing significant problems on the tracker, and so we were forced
to disable his account. This disabling does not need to be permanent.
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-
ng os specific rather than file system type specific is the usability bug.
But to fix it we'll need to introduce a 'filesystems' module enumerating
the different file systems we support, with tools for figuring out
what filesystem your program is talking to. But normacase still,
wouldn'
ened/closed in the past week that are *still* open or closed. So open
would certainly not be +2. I'm not sure if it would be +0 or -1 without
looking at the code.
I agree that having the delta against open from the previous week would
be the most helpful.
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
to tell the browser to
*stop* using basic auth.
> imagine that only "ultra geeks" know their URIs (I have no idea what the
> URI for a Google account is). But, I don't see this as being worthwhile
Well, my OpenId is 'david.bitdance.com', so even if you could get aro
I still intend to continue working on email6. There are many
other bugs in the current email package that require a rewrite of parts
of its infrastructure, and the email-sig is agreed that the email API
needs revision quite apart from the bytes/string issues. However, there
is something pleasing
On Sat, 02 Oct 2010 19:15:57 -0500, Benjamin Peterson
wrote:
> 2010/10/2 R. David Murray :
> > Regardless of whether or not this patch or a descendant thereof is
> > accepted I still intend to continue working on email6. =C2=A0There are ma=
> ny
> > other bugs in the cu
On Mon, 04 Oct 2010 12:32:26 -0400, Scott Dial
wrote:
> On 10/2/2010 7:00 PM, R. David Murray wrote:
> > The clever hack (thanks ultimately to Martin) is to accept 8bit data
> > by encoding it using the ASCII codec and the surrogateescape error
> > handler.
>
> I&#x
On Tue, 05 Oct 2010 22:05:33 +1000, Nick Coghlan wrote:
> On Tue, Oct 5, 2010 at 3:41 PM, Stephen J. Turnbull
> wrote:
> > R. David Murray writes:
> > > Only if the email package contains a coding error would the
> > > surrogates escape and cause problems for user
with bytes sometimes and strs sometimes.
>
> Please provide a way to return strs-with-surrogates if I ask for them.
Does my proposal make sense? But note, it raises exactly the backward
compatibility concerns you mention in your next email (that I will r
On Wed, 06 Oct 2010 22:55:00 +0900, "Stephen J. Turnbull"
wrote:
> R. David Murray writes:
>
> > version of headers to the email5 API, but since any such data would
> > be non-RFC compliant anyway, [access to non-conforming headers by
> > reparsing the bytes
On Thu, 07 Oct 2010 03:31:34 +0900, "Stephen J. Turnbull"
wrote:
> R. David Murray writes:
>
> > 5. Return the content, with non-ASCII bytes replaced with ?
> > characters.
>
> That hadn't occurred to me (and it makes me sick to contemplate it)
Stephen J. Turnbull xemacs.org> writes:
> R. David Murray writes:
> > We're (in the current patch) not punting on handling non-conforming
> > email, we're punting on handling non-conforming bytes *if the headers
> > that contain them need to be mo
t all programs
using difflib use it to generate diffs for direct output. (2) might
be worth it given that there is a "standard" to follow so it might be
worth coding that standard into the stdlib.
> Orthogonal: *After* a decision is made for
On Thu, 07 Oct 2010 15:00:04 +0900, "Stephen J. Turnbull"
wrote:
> R. David Murray writes:
>
> > > But that's not interesting; you did that with Python 3. We want to
> > Of course I did it with Python3. It's the Python3 email codebase
>
On Thu, 07 Oct 2010 16:03:18 -, l...@rmi.net wrote:
> I'm forwarding a link to the code of these clients to David by
> private email in case they might be useful as a test case (O'Reilly
> has already posted them ahead of the book, but they may be a bit too
> heavy for
vocate here.
Obviously the issues directly affect you, so hopefully it is worth
your time to engage us on this topic.
And thank you for the messages you have sent. I know they have made
me even more careful than I was already trying to be.
--
R. David Murray
g at, although in
practice I think you have to hang wire-format and text-format bits off
of appropriate places in the model in order to keep everything properly
coordinated.
> Maybe even in email5
I suspect that's pushing it. Patches happily accepted, though :)
--
R. David Murray
On Fri, 08 Oct 2010 15:44:45 -, l...@rmi.net wrote:
> Thanks for both your reply and work, David. I'm going to have
> to test my email clients under the 3.2 patch when it gels. It's
> good to hear that email5 API support remains a goal.
I just landed the patch (thou
n the direction of structure
by breaking lines at "obvious" places like ';'s. (Which line breaking
algorithm is the subject of at least one bug report)
I'd like to fix that in email6 by adding full support for structured
headers.
--
R. David Murray
et sorted out).
>
> I don't understand why this is difficult. As far as what Unicode has
It isn't difficult in principle. It's just difficult in email5.
--
R. David Murray www.bitdance.com
___
On Sat, 09 Oct 2010 02:48:23 +0900, "Stephen J. Turnbull"
wrote:
> R. David Murray writes:
> > On Sat, 09 Oct 2010 01:06:29 +0900, "Stephen J. Turnbull"
> wrote:
> > > That mess is entirely unnecessary in Python 3. Text and wire format
> > >
an end to that naming scheme, and that's a shame.
>
> Anyway, I can always alias pysetup to cheeseshop or ohmightytim on my
> machine and reminisce.
Or thebookofarmaments.
--
R. David Murray www.bitdance.com
___
s of Python's
normal backward compatibility policy.
In other words, you should move this discussion to python-ideas.
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
h
version of Python.
I don't use Windows much, but on balance I think I'm with Martin here :)
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
t?
Good question :)
When I added this it seemed like such a simple thing. Maybe the
endianness issue is the one to look at, despite the pass on Solaris.
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
following issues
> could be commited: 4499, 678250, 730467.
I've committed #9862, #4499 and #678250. I'd like a confirming opinion
on #730467, though it sounds reasonable to me.
--
R. David Murray www.bitdance.com
___
l Stutzbach and I are (were) two users of the second meaning. Itâs
> more useful to follow Raymondâs meaning, so that a simple query can find
> all accepted patches that are awaiting commit.
>
> I donât remember if I took up this use from R. David Murray or someone
> else,
ing it 'unit test needed', but if
people would rather change it back to just 'test needed', I will raise
no objection, since in practice trying to squeeze the meaning I wanted
into the stage field doesn't really work.
--
R. David Murray www.b
tting users groups to participate).
I'll be around and able to participate that weekend except for evening
US Eastern time.
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
h
ducing a new directory and having multiple files that cross-import
> one another.
+1 (or more)
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/list
On Tue, 26 Oct 2010 16:46:15 -0400, Michael Foord wrote:
> On 26/10/2010 15:05, R. David Murray wrote:
> > On Tue, 26 Oct 2010 10:39:19 -0700, Raymond
> > Hettinger wrote:
> >> If someone wants to reorganize code for clarity, I would prefer keeping
> >> it
d I'm not saying that packages are always bad.
I'm just saying that packages are also not always good; and, further,
that the number of lines of code in a file should, IMO, have nothing to
do with the decision as to whether or not to create a packa
But the reality is that almost all those Python2 users are future Python3
users, so they *are* the future user base. And like Georg said, as far
as we can see Python3 uptake is pretty much right on the schedule that
was predicted when it was first released.
--
R. David
es of 2.7 are worth the effort, we will, I'm
sure, continue to produce them.
What *new features* are needed in 2.x? I think the effort required
to set up and maintain a fork is a good measure of whether or not such
features are *valuable enough* to be worth doing. If they are, someone
will do
eems like it would need to be documented, even though
it would in a lot of cases just be used through assertEqual.
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyth
On Sat, 30 Oct 2010 18:36:45 +0200, Antoine Pitrou wrote:
> On Sat, 30 Oct 2010 12:02:27 -0400
> "R. David Murray" wrote:
> >
> > I don't disagree with this simplification, but given that you all want
> > to pare down the unittest API, I'd be in
7;s no biggie to have an optional style argument for basicConfig.
> People who don't use it don't have to specify it; the style argument would
> only
> apply if format was specified.
>
> For some people, use of {} over % is more about personal taste than about the
>
hm is stable, which means the above
> behaviour is a feature. I see no easy way of eliminating the O(n*n)
> issue. Custom key functions can't work in all cases.
Even granting some theoretical way to sort sets by their contents, it
still wouldn't be a bu
le,
so that is in fact *not* an invariant:
>>> x = ['abcd', 'foo'*50, 'foo'*50, 'dkke']
>>> y = x[::-1]
>>> [id(n) for n in sorted(x)]
[3073747680, 3073747904, 3073747624, 3073747512]
>>> [id(n) for n in sorted(y)]
[3073747680,
On Mon, 01 Nov 2010 15:14:36 -, Michael Foord
wrote:
> On 01/11/2010 15:10, R. David Murray wrote:
> > On Mon, 01 Nov 2010 14:26:19 -, Michael
> > Foord wrote:
> >> Well, bug is the wrong word as it is obviously an intended feature (or
> >> consequ
ured a limit on the
> > open
> > files or maybe of child processes on this buildbot or not, or if it is a
> > failure in Python?
>
> Before David responds: feel free to put temporarily a "limits -a"
> command into the build process, or some such.
You might als
n" and "closed"
> deltas is already quite an achievement and shows that our triage works.
Agreed.
We did have negative open deltas for several weeks running in October.
Kudos to everyone involved, and lets do it some more :) I&
resolved soon.
FYI bugs.python.org and www.python.org are different machines, and
in fact the two machines are not even hosted at the same location.
Valery, I would advise you to submit the patch to bugs.python.org when
it comes back up. Patches posted to this mailing list will in general
for a while before doing an
actual deprecation. Now that deprecation warnings are silent
by default we'll probably never need PendingDeprecationWarning ever
again :)
--David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.or
On Mon, 08 Nov 2010 18:10:17 -0600, Ron Adam wrote:
> def _private_api():
> #
> # Isn't it a good practice to use comments here?
> #
> ...
IMO, no.
--
R. David Murray www.bitdance.com
__
ode to deal with.
I think Tres was referring to certain packages (which shall remain
nameless since I don't feel like googling to find one) whose
documentation recommends the 'from import *' methodology.
At least that's how I read "Module writers who..." (that is,
s.python.org/issue1553375
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/
r this list. The question was "why did you developers drop this
(obscure) feature that we depend on in Python3?" I don't think that
question would make sense on python-list. Granted, there's a fuzzy
line there, but pylint is really development infrastructure :)
The pyth
processing of non-RFC conformant data.
I want to look at the CGI issue, but I'm not sure when I'll get to it.
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://
ng written the above, I googled for UCS-2 and got the Wikipedia
article on UTF16/UCS-2 [1]. Scanning that article, I do not see anything
that would clue me in to the problems of slicing strings in a Python
narrow build. Indeed, reading that article with my limited unicode
knowledge, if I were told P
On Sun, 21 Nov 2010 10:17:57 -0800, Raymond Hettinger
wrote:
> On Nov 21, 2010, at 9:38 AM, R. David Murray wrote:
> > I'm sorry, but I have to disagree. As a relative unicode ignoramus,
> > "UCS-2" and "UCS-4" convey almost no information to me, and the
On Sun, 21 Nov 2010 19:59:54 -0800, Glenn Linderman
wrote:
> On 11/21/2010 9:18 AM, R. David Murray wrote:
> > I want to look at the CGI issue, but I'm not sure when I'll get to it.
>
> Actually, since this code was working before 3.x, and if email.parser
> can n
`, the
faq/extending.rst: ... print('UCS4 build')
faq/extending.rst: ... print('UCS2 build')
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://m
On Mon, 22 Nov 2010 12:37:59 -0500, Alexander Belopolsky
wrote:
> On Mon, Nov 22, 2010 at 12:30 PM, R. David Murray
> wrote:
> ..
> > For reference, a grep in py3k/Doc reveals that there are currently exactly
> > 23 lines mentioning UCS2 or UCS4 in the docs.
>
> Did
>> Ah. Well, I can assure you that it's not the oldest trick in the book,
>> and not everyone uses it.
> ...
> Can't this just be enabled for platforms where it's known to work and let
> Python as it currently is for the users of these legacy systems ?
Ah, but that
ote: the Os/X universal seems to include a Tix runtime for the
non-Intel processor, but not for the Intel processor. This
makes me think there is a build problem.
-- Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mailing
Bob Ippolito wrote:
> On 9/30/06, Scott David Daniels <[EMAIL PROTECTED]> wrote:
>> Christos Georgiou wrote:
>>> Does anyone know why this happens? I can't find any information pointing to
>>> this being deliberate.
>> Also note: the Os/X univ
fval)
{ ...
if (fval == 0.0 && raw_match(&fval, cached)) {
PY_INCREF(cached);
return cached;
}
...
--
-- Scott David Daniels
[EMAIL PROTECTED]
___
Python-Dev mai
as incorrect, and have work-arounds. As these files now show
> up with "no extension", I rather expect that the work-around
> won't trigger, and the default behavior will be the correct one.
c) Given a filename, make an appropriately named associated file.
pyo_name =
efer Python because it uses smaller and more namespaces
> which are more specific and well defined. If we add email and compression
> functions to bytes, why not adding a web browser to the str?
As MAL says, the codec machinery is a general purpose too
On Fri, 03 Dec 2010 11:14:56 -0500, Alexander Belopolsky
wrote:
> On Fri, Dec 3, 2010 at 10:11 AM, R. David Murray
> wrote:
> ..
> > Please also recall that transform/untransform was discussed before
> > the release of Python 3.0 and was approved at the time, but it
I understand all four
of these to be "versions of xxx that won't raise". I think that's
a reasonable use of the word 'safe', but perhaps there is something
better.
SafeConfigParser doesn't follow that pattern, of course, though it
is perhaps true that it would raise er
7;t at the moment), it seems to make sense from an implementation
standpoint as well.
Like Ãric, I'm not sure what the implications of the existing module
having been released in 2.7 and 3.2 beta are in terms of making such an
API change.
--
R. David Murray
re lots
more out there[*]. I do especially like the fact that there is one in the
stdlib :)
It seems like the status quo is fine. I wouldn't object to it being
made more consistent. I would object to removing the existing cases.
--
R. David Murray www.bit
un directly. In 3.2, this means it will never show up
normally, since you can't even run the .pyc file without moving it out of
__pycache__. Which means 'ddir' is henceforth useful only to those people
who want to package sourceless distributions of the python code. (If
'12,345'
> ...
> >>> "UK says {value:,@uk} and France says
> {value:,@france}".format(value=12345, uk=uk_loc, france=france_loc)
> 'UK says 1,234.5 and France says 1 234,5'
>
> Comments?
There was at least one long thread on this on py
s "actual, expected"... And yet "expected,
> actual" still looks weird to me. :-(
You aren't unique, I feel the same way. But it seems to me that the most
important thing is to be consistent, so that I don't freak out for long.
--
R. David Murray
t; let developers act more quickly on bug reports. I wonder if this output
> really speeds up the process.
>
> Do you have an example bug where this patch helps in finding the precise
> location of a segfault?
How is 'line 29 in g' not more precise
essage. *format* is
> + an ASCII-encoded string.
So, the former, I'd guess :)
--
R. David Murray www.bitdance.com
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/lis
with
the 8th bit set, leaving no room for interpretation. So presumably
you mean it is (treated as) an ISO-8859-1 encoded string, despite the
function name?
--
R. David Murray www.bitdance.com
___
Python-Dev mailing
On Tue, 28 Dec 2010 13:58:24 +0100, Victor Stinner
wrote:
> Le mardi 28 décembre 2010 à 11:40 +0100, "Martin v. Löwis" a écrit :
> > Am 28.12.2010 11:28, schrieb Victor Stinner:
> > > Le lundi 27 décembre 2010 à 23:07 -0500, R. David Murray a écrit :
> &g
1601 - 1700 of 2106 matches
Mail list logo
