On 1/17/07, Thomas Heller <[EMAIL PROTECTED]> wrote:
> Why don't the Python 2.5 buildbots build anymore?
It looks like there were no checkins that caused a build. Changing
doc or Misc/NEWS is excluded. I'm guessing that there is a bug in
buildbot that causes it to miss any changes from svnmerge.
Larry Hastings <[EMAIL PROTECTED]> wrote:
> I just ran a quickie experiment and determined: when leaving a scope,
> variables are deleted FIFO, aka in the same order they were created.
> This surprised me; I'd expected them to be deleted LIFO, aka last
> first. Why is it thus? Is this behavi
I just ran a quickie experiment and determined: when leaving a scope,
variables are deleted FIFO, aka in the same order they were created.
This surprised me; I'd expected them to be deleted LIFO, aka last
first. Why is it thus? Is this behavior an important feature or an
irrelevant side-e
On Jan 17, 2007, at 6:22 PM, Anthony Baxter wrote:
> On Wednesday 17 January 2007 05:52, James Y Knight wrote:
>> Yes, this is it. As a refinement: if the New Way can easily be
>> backported to 2.5,
>
> Um - 2.5 is _done_. Released. In maintenance mode. New features will
> not be getting backporte
On Wednesday 17 January 2007 05:52, James Y Knight wrote:
> Yes, this is it. As a refinement: if the New Way can easily be
> backported to 2.5,
Um - 2.5 is _done_. Released. In maintenance mode. New features will
not be getting backported to a 2.5.x release.
Anthony
--
Anthony Baxter <[EM
A.M. Kuchling <[EMAIL PROTECTED]> wrote:
> http://www.python.org/sf/1599254 is a bug in the mailbox.py module
> that affects single-file mailbox formats (mbox, Babyl, MMDF)
> and can cause data loss.
I can't speak for MMDF or Babyl, but it's a well-known requirement that all
programs on a system m
http://www.python.org/sf/1599254 is a bug in the mailbox.py module
that affects single-file mailbox formats (mbox, Babyl, MMDF)
and can cause data loss.
A proposed fix, mailbox-unified-patch, is attached to the bug. If you
use mailbox.py for modifying mailboxes in the above formats, can you
pleas
Why don't the Python 2.5 buildbots build anymore?
http://www.python.org/dev/buildbot/2.5/
Thanks,
Thomas
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/o
On 1/17/07, Thomas Wouters <[EMAIL PROTECTED]> wrote:
> On 1/16/07, Jim Jewett <[EMAIL PROTECTED]> wrote:
> > Other than dict.items (and .keys and .values) returning a non-list,
> > are there any other cases where the Py3K idiom can't already be used
> > in (or at least backported to) Py 2.x?
> Th
On 1/16/07, Neal Norwitz <[EMAIL PROTECTED]> wrote:
http://python.org/sf/1637022 points out a problem caused by the lack
of a _Py prefix on Ellipsis. Most (all?) of the new AST names are not
prefixed. These are all meant to be internal names. Are there any
issues with changing this? If we do
On 1/16/07, Jim Jewett <[EMAIL PROTECTED]> wrote:
Other than dict.items (and .keys and .values) returning a non-list,
are there any other cases where the Py3K idiom can't already be used
in (or at least backported to) Py 2.x?
Well, there is that bit where strings are all unicode, including al
"James Y Knight" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
| Everyone will continue to code in a
| 2.5-compatible dialect for the immediate future, because their code
| needs to continue to function in 2.5.
?? But once 2.6 and 3.0 come out, there will be some to many who don'
12 matches
Mail list logo
