Re: [Python-Dev] iterator API in Py3.0

2006-03-04 Thread Phillip J. Eby
At 04:44 PM 3/4/2006 -0500, Raymond Hettinger wrote: >> As far as I can understand your position, you seem to be arguing that >> whatever we have now is correct, and therefore changing it would be wrong. > >Yes, that's pretty much it. IMO, introducing __builtin__.next() would >suck. The sublime

Re: [Python-Dev] Another Windows buildbot slave

2006-03-04 Thread Josiah Carlson
Josiah Carlson <[EMAIL PROTECTED]> wrote: > It took me a while to get it set up, but we've got another Windows XP > buildbot slave running. Spoke too soon, not quite ready yet. - Josiah ___ Python-Dev mailing list Python-Dev@python.org http://mail.py

[Python-Dev] Another Windows buildbot slave

2006-03-04 Thread Josiah Carlson
It took me a while to get it set up, but we've got another Windows XP buildbot slave running. - Josiah ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/op

Re: [Python-Dev] iterator API in Py3.0

2006-03-04 Thread Phillip J. Eby
At 12:05 AM 3/5/2006 +0300, Oleg Broytmann wrote: >On Sat, Mar 04, 2006 at 03:45:03PM -0500, Phillip J. Eby wrote: > > At 09:34 AM 3/4/2006 -0800, Anna Ravenscroft wrote: > > >I think this is a really good point. next() is supposed to get used, by > > >coders, in regular code - so it shouldn't be _

Re: [Python-Dev] iterator API in Py3.0

2006-03-04 Thread Phillip J. Eby
At 04:11 PM 3/4/2006 -0500, Raymond Hettinger wrote: >[Anna Ravenscroft] >>>I think this is a really good point. next() is supposed to get used, by >>>coders, in regular code - so it shouldn't be __next__. I can understand >>>the desire for both forms, although that seems it would clutter things

Re: [Python-Dev] iterator API in Py3.0

2006-03-04 Thread Raymond Hettinger
[Anna Ravenscroft] >>I think this is a really good point. next() is supposed to get used, by >>coders, in regular code - so it shouldn't be __next__. I can understand the >>desire for both forms, although that seems it would clutter things up >>unnecessarily - particularly if the two do the same

Re: [Python-Dev] iterator API in Py3.0

2006-03-04 Thread Oleg Broytmann
On Sat, Mar 04, 2006 at 03:45:03PM -0500, Phillip J. Eby wrote: > At 09:34 AM 3/4/2006 -0800, Anna Ravenscroft wrote: > >I think this is a really good point. next() is supposed to get used, by > >coders, in regular code - so it shouldn't be __next__. I can understand > >the desire for both forms,

Re: [Python-Dev] iterator API in Py3.0

2006-03-04 Thread Phillip J. Eby
At 09:34 AM 3/4/2006 -0800, Anna Ravenscroft wrote: >I think this is a really good point. next() is supposed to get used, by >coders, in regular code - so it shouldn't be __next__. I can understand >the desire for both forms, although that seems it would clutter things up >unnecessarily - partic

Re: [Python-Dev] iterator API in Py3.0

2006-03-04 Thread Anna Ravenscroft
On 3/3/06, Raymond Hettinger <[EMAIL PROTECTED]> wrote: [Aahz]> * As a writer/teacher, I want to be able to say, "All Python special> methods have leading and trailing double-underscore."  Period, end of> story.When teaching your classes, do you sense an aversion to using double underscore methods

Re: [Python-Dev] My buildbot host upgraded to OSX 10.4

2006-03-04 Thread Martin v. Löwis
[EMAIL PROTECTED] wrote: > I upgraded my PowerMac G5 to OSX 10.4. ZopeInterface isn't recompiling > after the upgrade to XCode 2.1. You probably ought to just pull "g5 osx.3" > from the buildbot host list, certainly until I have time to figure this > problem out. (Probably after as well. My mac

Re: [Python-Dev] My buildbot host upgraded to OSX 10.4

2006-03-04 Thread skip
skip> I upgraded my PowerMac G5 to OSX 10.4. ZopeInterface isn't skip> recompiling after the upgrade to XCode 2.1. Okay, my buildbot slave is back online. Still, feel free to kick it out if you think it's not worth it to continue running it. Skip _

[Python-Dev] My buildbot host upgraded to OSX 10.4

2006-03-04 Thread skip
I upgraded my PowerMac G5 to OSX 10.4. ZopeInterface isn't recompiling after the upgrade to XCode 2.1. You probably ought to just pull "g5 osx.3" from the buildbot host list, certainly until I have time to figure this problem out. (Probably after as well. My machine configuration is now not sub

[Python-Dev] Outdated Python Info on www.unicode.org (fwd)

2006-03-04 Thread skip
Someone here (Martin, MAL, /F?) would probably be able to write a short, authoritative description of Python's Unicode powers. Any takers? Skip --- Begin Message --- The Unicode Consortium has a page about Unicode Enabled Products . This page con

[Python-Dev] FrOSCon 2006 - Call for {Papers|Projects}

2006-03-04 Thread M.-A. Lemburg
Is anyone interested in having a Python track at this conference ? PS: The EuroPython conference takes place in Geneva, one week later. Original Message Subject: FrOSCon 2006 - Call for {Papers|Projects} Date: Fri, 03 Mar 2006 16:39:08 +0100 From: Sebastian Bergmann Organizatio

Re: [Python-Dev] __exit__ API?

2006-03-04 Thread Nick Coghlan
Guido van Rossum wrote: > A few days ago there were rumbling noises that requiring __exit__ to > re-raise the exception (as I amended PEP 343 at the time) could lead > to easily-missed bugs in __exit__ handlers. > > After thinking it over I think I agree and I think I'd like to change > the API so

Re: [Python-Dev] Bug in from __future__ processing?

2006-03-04 Thread Anthony Baxter
On Saturday 04 March 2006 15:34, Tim Peters wrote: > Indeed! But whose arm could we twist to get them to repair the > compiler in 2.4? I'd settle for a blurb in the next 2.4 NEWS just > noting that 2.5 will follow the documented syntax. That may even > be desirable, to avoid breaking working (al