Re: [Python-Dev] 2.5 PEP
On Thursday 16 February 2006 17:06, Martin v. Löwis wrote: I'm still unhappy with that change, and still nobody has told me how to maintain PyXML so that it can continue to work both for 2.5 and for 2.4. Martin, I do intend to write a proper response for you, but have been massively swamped. python-dev topics occaissionally pop up for me, but time has been too limited to get back to the important items, like this one. -Fred -- Fred L. Drake, Jr. fdrake at acm.org ___ 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] 2.5 PEP
(my mails to python-dev are bouncing; guess that's what you get when you question the PSF's ability to build web sites... trying again.) Neal Norwitz wrote: (is the xmlplus/xmlcore issue still an issue, btw?) What issue are you talking about? the changes described here http://mail.python.org/pipermail/python-dev/2005-December/058710.html I'd like to propose that a new package be created in the standard library: xmlcore. which led to this response from a pyxml maintainer: http://mail.python.org/pipermail/python-dev/2005-December/058752.html I don't agree with the change. You just broke source compatibility between the core package and PyXML. /F ___ 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] 2.5 PEP
Neal Norwitz wrote: On 2/15/06, Alain Poirier [EMAIL PROTECTED] wrote: - isn't the current implementation of itertools.tee (cache of previous generated values) incompatible with the new possibility to feed a generator (PEP 342) ? I'm not sure what you are referring to. What is the issue? The 'tee' object doesn't have a send method. (This is true for all of the itertools iterators, I believe). The request is misguided though - the itertools module is designed to operate on output-only iterators, not on generators that expect input via send(). Because the output values might depend on the values sent, then it makes no sense to cache them (or do most of the other things itertools does). The relevant functionality would actually make the most sense as a fork() method on generators, but PEP 342 was trying to be fairly minimalist. Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- http://www.boredomandlaziness.org ___ 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] 2.5 PEP
(is the xmlplus/xmlcore issue still an issue, btw?) What issue are you talking about? the changes described here http://mail.python.org/pipermail/python-dev/2005-December/058710.html I'd like to propose that a new package be created in the standard library: xmlcore. which led to this response from a pyxml maintainer: http://mail.python.org/pipermail/python-dev/2005-December/058752.html I don't agree with the change. You just broke source compatibility between the core package and PyXML. /F ___ 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] 2.5 PEP
Fredrik Lundh wrote: http://mail.python.org/pipermail/python-dev/2005-December/058752.html I don't agree with the change. You just broke source compatibility between the core package and PyXML. I'm still unhappy with that change, and still nobody has told me how to maintain PyXML so that it can continue to work both for 2.5 and for 2.4. Regards, Martin ___ 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] 2.5 PEP
Hi, 2 questions: - is (c)ElementTree still planned for inclusion ? - isn't the current implementation of itertools.tee (cache of previous generated values) incompatible with the new possibility to feed a generator (PEP 342) ? Regards Neal Norwitz a écrit : Attached is the 2.5 release PEP 356. It's also available from: http://www.python.org/peps/pep-0356.html Does anyone have any comments? Is this good or bad? Feel free to send to me comments. We need to ensure that PEPs 308, 328, and 343 are implemented. We have possible volunteers for 308 and 343, but not 328. Brett is doing 352 and Martin is doing 353. We also need to resolve a bunch of other implementation details about providing the C AST to Python, bdist_* issues and a few more possible stdlib modules. Don't be shy, tell the world what you think about these. Can someone go through PEP 4 and 11 and determine what work needs to be done? The more we distribute the work, the easier it will be on everyone. You don't really want to listen to me whine any more do you? ;-) Thank you, ___ 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] 2.5 PEP
On Tue, Feb 14, 2006 at 09:58:46PM -0800, Neal Norwitz wrote: We need to ensure that PEPs 308, 328, and 343 are implemented. We have possible volunteers for 308 and 343, but not 328. Brett is doing 352 and Martin is doing 353. I can volunteer for 328 if no one else wants it, I've messed with the import mechanism before (and besides, it's fun.) I've also written an unfinished 308 implementation to get myself acquainted with the AST code more. 'Unfinished' means that it works completely, except for some cases of ambiguous syntax. I can fix that in a few days if the deadline nears and there's no working patch. (Naively adding if/else expressions broke list comprehensions with an 'if' clause, and fixing that broke list comprehensions with 'for x in lambda:0, lambda:1', and fixing that broke list comprehensions altogether... I added clean up Grammar file to the PyCon core sprint topics for that reason. I guess 308 wasn't as much a trainer implementation as people thought ;) The syntax part of 328 is probably easier (but the rest isn't.) Access to C AST from Python If this still needs work when I finish grokking the AST code and the PyObj branch of it, I can help. I should have more than enough spare time to finish these things before alpha 1. -- Thomas Wouters [EMAIL PROTECTED] Hi! I'm a .signature virus! copy me into your .signature file to help me spread! ___ 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] 2.5 PEP
On Wed, Feb 15, 2006, Thomas Wouters wrote: I can volunteer for 328 if no one else wants it, I've messed with the import mechanism before (and besides, it's fun.) I've also written an unfinished 308 implementation to get myself acquainted with the AST code more. 'Unfinished' means that it works completely, except for some cases of ambiguous syntax. I can fix that in a few days if the deadline nears and there's no working patch. If you want to also take over the PEP328 editing, please be my guest. I keep making time for it that gets overridden by other things. -- Aahz ([EMAIL PROTECTED]) * http://www.pythoncraft.com/ 19. A language that doesn't affect the way you think about programming, is not worth knowing. --Alan Perlis ___ 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] 2.5 PEP
Alain Poirier wrote: - is (c)ElementTree still planned for inclusion ? It is included already. Regards, Martin ___ 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] 2.5 PEP
Martin v. Löwis wrote: - is (c)ElementTree still planned for inclusion ? It is included already. in the xml.etree package, in case someone's looking for it in the usual place. that is, import xml.etree.ElementTree as ET import xml.etree.cElementTree as ET will work in any 2.5 that has a working pyexpat. (is the xmlplus/xmlcore issue still an issue, btw?) /F ___ 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] 2.5 PEP
Neal Norwitz wrote: Attached is the 2.5 release PEP 356. It's also available from: http://www.python.org/peps/pep-0356.html Does anyone have any comments? Is this good or bad? Feel free to send to me comments. We need to ensure that PEPs 308, 328, and 343 are implemented. We have possible volunteers for 308 and 343, but not 328. Brett is doing 352 and Martin is doing 353. PEP 338 is pretty much ready to go, too - just waiting on Guido's review and pronouncement on the specific API used in the latest update (his last PEP parade said he was OK with the general concept, but I only posted the PEP 302 compliant version after that). Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- http://www.boredomandlaziness.org ___ 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] 2.5 PEP
On 2/15/06, Fredrik Lundh [EMAIL PROTECTED] wrote: (is the xmlplus/xmlcore issue still an issue, btw?) What issue are you talking about? 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
Re: [Python-Dev] 2.5 PEP
On 2/15/06, Alain Poirier [EMAIL PROTECTED] wrote: - isn't the current implementation of itertools.tee (cache of previous generated values) incompatible with the new possibility to feed a generator (PEP 342) ? I'm not sure what you are referring to. What is the issue? 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
[Python-Dev] 2.5 PEP
Attached is the 2.5 release PEP 356. It's also available from: http://www.python.org/peps/pep-0356.html Does anyone have any comments? Is this good or bad? Feel free to send to me comments. We need to ensure that PEPs 308, 328, and 343 are implemented. We have possible volunteers for 308 and 343, but not 328. Brett is doing 352 and Martin is doing 353. We also need to resolve a bunch of other implementation details about providing the C AST to Python, bdist_* issues and a few more possible stdlib modules. Don't be shy, tell the world what you think about these. Can someone go through PEP 4 and 11 and determine what work needs to be done? The more we distribute the work, the easier it will be on everyone. You don't really want to listen to me whine any more do you? ;-) Thank you, n PEP: 356 Title: Python 2.5 Release Schedule Version: $Revision: 42375 $ Author: Neal Norwitz, GvR Status: Draft Type: Informational Created: 07-Feb-2006 Python-Version: 2.5 Post-History: Abstract This document describes the development and release schedule for Python 2.5. The schedule primarily concerns itself with PEP-sized items. Small features may be added up to and including the first beta release. Bugs may be fixed until the final release. There will be at least two alpha releases, two beta releases, and one release candidate. The release date is planned 30 September 2006. Release Manager TBD (Anthony Baxter?) Martin von Loewis is building the Windows installers, Fred Drake the doc packages, and TBD (Sean Reifschneider?) the RPMs. Release Schedule alpha 1: May 6, 2006 [planned] alpha 2: June 3, 2006 [planned] alpha 3: July 1, 2006 [planned] beta 1: July 29, 2006 [planned] beta 2: August 26, 2006 [planned] rc 1:September 16, 2006 [planned] final: September 30, 2006 [planned] Completed features for 2.5 PEP 309: Partial Function Application PEP 314: Metadata for Python Software Packages v1.1 (should PEP 314 be marked final?) PEP 341: Unified try-except/try-finally to try-except-finally PEP 342: Coroutines via Enhanced Generators - AST-based compiler - Add support for reading shadow passwords (http://python.org/sf/579435) - any()/all() builtin truth functions - new hashlib module add support for SHA-224, -256, -384, and -512 (replaces old md5 and sha modules) - new cProfile module suitable for profiling long running applications with minimal overhead Planned features for 2.5 PEP 308: Conditional Expressions (Someone volunteered on python-dev, is there progress?) PEP 328: Absolute/Relative Imports (Needs volunteer, mail python-dev if interested) PEP 343: The with Statement (nn: I have a possible volunteer.) Note there are two separate implementation parts: interpreter changes and python code for utilities. PEP 352: Required Superclass for Exceptions (Brett Cannon is expected to implement this.) PEP 353: Using ssize_t as the index type MvL expects this to be complete in March. Access to C AST from Python Add bdist_msi to the distutils package. (MvL wants one more independent release first.) Add bdist_deb to the distutils package? (see http://mail.python.org/pipermail/python-dev/2006-February/060926.html) Add bdist_egg to the distutils package??? Add setuptools to the standard library. Add wsgiref to the standard library. (GvR: I have a bunch more that could/would/should be added. -- Still true?) Deferred until 2.6: - None Open issues This PEP needs to be updated and release managers confirmed. - Review PEP 4: Deprecate and/or remove the modules - Review PEP 11: Remove support for platforms as described Copyright This document has been placed in the public domain. Local Variables: mode: indented-text indent-tabs-mode: nil End: ___ 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
