Re: [Python-Dev] outstanding items for 2.5
On Mon, Apr 03, 2006, Guido van Rossum wrote: > > Done. What exactly do you plan to do apart from editing the docs to > steer people away from file()? For the initial checkin, the dirt-simple: def open(filename, *args, **kwargs): return file(filename, *args, **kwargs) At this point, the sole purpose is to kill open() as a simple alias for file() and turn it into a factory function that can be documented separately (and have its own help() info). Further extensions can be done later. Because this is file I/O, there is no reason to even think of performance improvements in the call. -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ "Look, it's your affair if you want to play with five people, but don't go calling it doubles." --John Cleese anticipates Usenet ___ 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
Re: [Python-Dev] outstanding items for 2.5
Done. What exactly do you plan to do apart from editing the docs to steer people away from file()? --Guido On 4/3/06, Aahz <[EMAIL PROTECTED]> wrote: > On Sun, Apr 02, 2006, Neal Norwitz wrote: > > > > I updated the PEP to include owners. If this message is sent directly > > to you, you are an owner. > > > > http://www.python.org/dev/peps/pep-0356/ > > > > Review the PEP and let me know what needs to be changed. If your pet > > project isn't already in the PEP, assume it has been deferred until > > 2.6. > > Per "file() vs open(), round 7" at > http://mail.python.org/pipermail/python-dev/2005-December/thread.html#59073 > please add to list of planned features and list me as the owner. I'd > calle this feature "make open() a factory function instead of an alias > for file() (with suitable doc changes)" -- that parenthetical being the > blocking factor here ;-) > -- > Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ > > "Look, it's your affair if you want to play with five people, but don't > go calling it doubles." --John Cleese anticipates Usenet > ___ > 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/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ 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
Re: [Python-Dev] outstanding items for 2.5
On Sun, Apr 02, 2006, Neal Norwitz wrote: > > I updated the PEP to include owners. If this message is sent directly > to you, you are an owner. > > http://www.python.org/dev/peps/pep-0356/ > > Review the PEP and let me know what needs to be changed. If your pet > project isn't already in the PEP, assume it has been deferred until > 2.6. Per "file() vs open(), round 7" at http://mail.python.org/pipermail/python-dev/2005-December/thread.html#59073 please add to list of planned features and list me as the owner. I'd calle this feature "make open() a factory function instead of an alias for file() (with suitable doc changes)" -- that parenthetical being the blocking factor here ;-) -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ "Look, it's your affair if you want to play with five people, but don't go calling it doubles." --John Cleese anticipates Usenet ___ 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
Re: [Python-Dev] outstanding items for 2.5
I checked what I owned. - pgen: yes, if I have time - GeneratorExit inheriting from BaseException: no, I've pronounced on this - StopIteration propagation from context managers: I'm giving this to Phillip --Guido On 4/3/06, Neal Norwitz <[EMAIL PROTECTED]> wrote: > I updated the PEP to include owners. If this message is sent directly > to you, you are an owner. > > http://www.python.org/dev/peps/pep-0356/ > > There are still some items without owners as I don't know who will be > leading the charge to get some of the modules in the stdlib. If we > don't have anyone pushing them, they won't go in. If they are going > in, they should be committed soon after alpha1 is out the door. > Please don't rush to get them in before the alpha, unless you're > absolutely sure it won't screw things up. > > Review the PEP and let me know what needs to be changed. If your pet > project isn't already in the PEP, assume it has been deferred until > 2.6. > > Also, now would be a good time to see if you have any bugs/patches > assigned to you: http://sourceforge.net/my/tracker.php > > Cheers, > n > -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ 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
Re: [Python-Dev] outstanding items for 2.5
On Sun, Apr 02, 2006 at 11:34:18PM -0800, Neal Norwitz wrote: > Review the PEP and let me know what needs to be changed. If your pet > project isn't already in the PEP, assume it has been deferred until > 2.6. I'd like to see Gregory K. Johnson's updated mailbox module (in sandbox/mailbox/) included. I mentored its development and think the code is ready for inclusion, but would like someone else to run an eye over it. Any volunteers? I can file a patch request for this item if desired. --amk ___ 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
[Python-Dev] outstanding items for 2.5
I updated the PEP to include owners. If this message is sent directly to you, you are an owner. http://www.python.org/dev/peps/pep-0356/ There are still some items without owners as I don't know who will be leading the charge to get some of the modules in the stdlib. If we don't have anyone pushing them, they won't go in. If they are going in, they should be committed soon after alpha1 is out the door. Please don't rush to get them in before the alpha, unless you're absolutely sure it won't screw things up. Review the PEP and let me know what needs to be changed. If your pet project isn't already in the PEP, assume it has been deferred until 2.6. Also, now would be a good time to see if you have any bugs/patches assigned to you: http://sourceforge.net/my/tracker.php Cheers, n ___ 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
