[Python-Dev] Holding a Python Language Summit at PyCon
The PyCon organizers are planning a Python Language Summit to be held in Chicago just before the conference, on Thursday March 26 2009. (This is the second day of tutorials, and the day before PyCon officially starts.) The purpose of the Python Language Summit is to let the developers of Python implementations discuss issues that affect us all, and to let the developers of a particular implementation discuss their own project-specific issues. PyCon brings a lot of the core developers together into one place and there's been a "Python core" sprint for a long time, but we haven't had a formal time and place for *discussion* among core developers. Attending the summit will be free; registration for PyCon is *not* included, but won't be required to attend the summit. I e-mailed some CPython, Jython, IronPython, PyPy, etc. developers asking for topic suggestions, and assembled a draft of a schedule from some of the most commonly mentioned topics; the current draft schedule is below. The schedule is very 'loose', leaving a fair bit of open space so that we can hopefully begin working on ideas arising from the discussion. * What do you think of the selected topics? * I'd like to have a champion for each session, who will make a brief presentation about the session's topic at the start, laying out the issues and possible courses of action to guide the resulting discussion. If you wish to volunteer as the champion for a session, please let me know. (Preference will be given to people actively working on the particular topic.) * For CPython, invitations will be sent to everyone with committer status (plus a few book authors, significant patch contributors who aren't committers yet, etc.). If you're not a committer but think you can contribute, please let me know privately. Also, please suggest other * There will probably be summit-related sponsorship opportunities for interested companies. Andrew M. Kuchling [EMAIL PROTECTED] Registration Manager, PyCon 2009 http://us.pycon.org 9:00 - 10:30 = Open discussion session 11:00 - 12:30 = Transition plan for rest of 2.x series; goals for 2.7/3.1. - New features & future plans? - Is 2.7 last of the 2.x releases? - Unicode issues - Stdlib plans? Champion needed. 12:30 - 14:00 = Lunch (probably provided by the PSF or a sponsor). 14:00 - 15:30 = Two tracks: Cross-implementation issues: What do the various VMs want/need from CPython to help with their implementations? * Marking CPython-specific tests in the test suite? * Getting an implementation agnostic test suite for the Python language? * Separating the language tests and the pure Python part of the stdlib into a separate project? (Or publish them as a separate package.) * Transition plans for 3.0? Champion needed. Package distribution & installation. * setting up an organized network of mirrors ? la CPAN * adding a commenting system on PyPI * think about a reference implementation for a PyPI client in the stdlib (XML-RPC client+upload and register) * improvments on packaging matters - this includes distutils but also setuptools. Champion needed. 16:00 - 17:30 = Free space for sprinting, hacking, further discussion, etc. 18:00-ish = Group dinners. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Holding a Python Language Summit at PyCon
On Wed, Dec 3, 2008 at 4:31 PM, A.M. Kuchling <[EMAIL PROTECTED]> wrote: > The PyCon organizers are planning a Python Language Summit to be held > in Chicago just before the conference, on Thursday March 26 2009. > (This is the second day of tutorials, and the day before PyCon > officially starts.) > [cut] > > Package distribution & installation. > > * setting up an organized network of mirrors ? la CPAN > * adding a commenting system on PyPI > * think about a reference implementation for a PyPI client in the >stdlib (XML-RPC client+upload and register) > * improvments on packaging matters - this includes distutils but >also setuptools. Hello, I'd like to volunteer for that part given the fact that I am currently working on the patches for the mirroring thing in a branch of PyPI. The work is described here : http://wiki.python.org/moin/PEP%20374 It changed a bit and I need to update it, but you get the idea there. I also have some work going on for distutils. You have a summary of the work going on in my blog http://tarekziade.wordpress.com/2008/11/26/python-package-distribution-my-current-work/ Regards Tarek > > Champion needed. > > > 16:00 - 17:30 > = > > Free space for sprinting, hacking, further discussion, etc. > > > 18:00-ish > = > > Group dinners. > ___ > Python-Dev mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/ziade.tarek%40gmail.com > -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/ ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Accessing source code in zipped packages
Georg Brandl wrote: > Alexander Belopolsky schrieb: >> About a month ago, I submitted two patches that address Pdb and >> doctest inability to load source code from modules with custom loaders >> such as modules loaded from zip files: >> >> http://bugs.python.org/issue4201 >> http://bugs.python.org/issue4197 >> >> The patches are very simple, basically calls to linecache.getline() >> need to be provided with the module's dict to enable linecache to find >> the module's __loader__. > > There is also http://bugs.python.org/issue4223 which goes in the same > direction. I've assigned all 3 of those to myself, since I've been meaning to look at some zipimport related stuff anyway (the things I'm looking at are 2.7/3.1 related though, so I was waiting for the 3.0 release to be cut first). We already missed the 2.6.1 deadline though. Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Holding a Python Language Summit at PyCon
Tarek Ziadé wrote: > Hello, > > I'd like to volunteer for that part given the fact that I am currently > working on the patches > for the mirroring thing in a branch of PyPI. > > The work is described here : http://wiki.python.org/moin/PEP%20374 > It changed a bit and I need to update it, but you get the idea there. For the record, when working on a PEP draft on the Wiki or Google docs, it's worth asking the PEP editors (or any of the SVN committers really) to reserve a PEP number once things start to progress to the point where folks need a common shorthand reference to the document. PEP 374 for example, is already a placeholder for the SVN to DVCS migration PEP: http://www.python.org/dev/peps/pep-0374/ We aren't going to run out of PEP numbers anytime soon - it's OK if some of them get "wasted" on draft PEPs that end up getting abandoned. (Better that than having multiple draft PEPs being referred to with the same number as appears to be the case at the moment). Cheers, Nick. -- Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia --- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Holding a Python Language Summit at PyCon
On Wed, Dec 3, 2008 at 9:44 PM, Nick Coghlan <[EMAIL PROTECTED]> wrote: > Tarek Ziadé wrote: >> Hello, >> >> I'd like to volunteer for that part given the fact that I am currently >> working on the patches >> for the mirroring thing in a branch of PyPI. >> >> The work is described here : http://wiki.python.org/moin/PEP%20374 >> It changed a bit and I need to update it, but you get the idea there. > > For the record, when working on a PEP draft on the Wiki or Google docs, > it's worth asking the PEP editors (or any of the SVN committers really) > to reserve a PEP number once things start to progress to the point where > folks need a common shorthand reference to the document. > > PEP 374 for example, is already a placeholder for the SVN to DVCS > migration PEP: > http://www.python.org/dev/peps/pep-0374/ > Right, I'll ask for a number and change it accordingly; Regards Tarek ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] RELEASED Python 3.0 final
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On behalf of the Python development team and the Python community, I am happy to announce the release of Python 3.0 final. Python 3.0 (a.k.a. "Python 3000" or "Py3k") represents a major milestone in Python's history, and was nearly three years in the making. This is a new version of the language that is incompatible with the 2.x line of releases, while remaining true to BDFL Guido van Rossum's vision. Some things you will notice include: * Fixes to many old language warts * Removal of long deprecated features and redundant syntax * Improvements in, and a reorganization of, the standard library * Changes to the details of how built-in objects like strings and dicts work * ...and many more new features While these changes were made without concern for backward compatibility, Python 3.0 still remains very much "Pythonic". We are confident that Python 3.0 is of the same high quality as our previous releases, such as the recently announced Python 2.6. We will continue to support and develop both Python 3 and Python 2 for the foreseeable future, and you can safely choose either version (or both) to use in your projects. Which you choose depends on your own needs and the availability of third-party packages that you depend on. Some other things to consider: * Python 3 has a single Unicode string type; there are no more 8-bit strings * The C API has changed considerably in Python 3.0 and third-party extension modules you rely on may not yet be ported * Tools are available in both Python 2.6 and 3.0 to help you migrate your code * Python 2.6 is backward compatible with earlier Python 2.x releases We encourage you to participate in Python 3.0's development process by joining its mailing list: http://mail.python.org/mailman/listinfo/python-3000 If you find things in Python 3.0 that are broken or incorrect, please submit bug reports at: http://bugs.python.org/ For more information, links to documentation, and downloadable distributions, see the Python 3.0 website: http://www.python.org/download/releases/3.0/ Enjoy, - -Barry Barry Warsaw [EMAIL PROTECTED] Python 2.6/3.0 Release Manager (on behalf of the entire python-dev team) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSTc3pXEjvBPtnXfVAQI69wP/dPHh8IL3GxziEV9QzlveKG+KyZb2X16x fxJnTCiXAbiAhT5C+m43OEnbF1PJgMDKtcZ5b7aQb4TQ0mJxISTQh0RfLCpArmlo tdTbzCLnh13KzB+3sUHCx+MeQNXERoWDV8hLz+4Ae71UsuUGynhtyP7ZJMJDue8j so2gv3fOMSs= =vkiy -END PGP SIGNATURE- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] RELEASED Python 3.0 final
Thanks so much for seeing this one through, Barry and co! Champagne!!! On Wed, Dec 3, 2008 at 5:51 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On behalf of the Python development team and the Python community, I am > happy to announce the release of Python 3.0 final. > > Python 3.0 (a.k.a. "Python 3000" or "Py3k") represents a major milestone in > Python's history, and was nearly three years in the making. This is a new > version of the language that is incompatible with the 2.x line of releases, > while remaining true to BDFL Guido van Rossum's vision. Some things you > will notice include: > > * Fixes to many old language warts > * Removal of long deprecated features and redundant syntax > * Improvements in, and a reorganization of, the standard library > * Changes to the details of how built-in objects like strings and dicts work > * ...and many more new features > > While these changes were made without concern for backward compatibility, > Python 3.0 still remains very much "Pythonic". > > We are confident that Python 3.0 is of the same high quality as our previous > releases, such as the recently announced Python 2.6. We will continue to > support and develop both Python 3 and Python 2 for the foreseeable future, > and you can safely choose either version (or both) to use in your projects. > Which you choose depends on your own needs and the availability of > third-party packages that you depend on. Some other things to consider: > > * Python 3 has a single Unicode string type; there are no more 8-bit strings > * The C API has changed considerably in Python 3.0 and third-party extension > modules you rely on may not yet be ported > * Tools are available in both Python 2.6 and 3.0 to help you migrate your > code > * Python 2.6 is backward compatible with earlier Python 2.x releases > > We encourage you to participate in Python 3.0's development process by > joining its mailing list: > >http://mail.python.org/mailman/listinfo/python-3000 > > If you find things in Python 3.0 that are broken or incorrect, please submit > bug reports at: > > http://bugs.python.org/ > > For more information, links to documentation, and downloadable > distributions, see the Python 3.0 website: > > http://www.python.org/download/releases/3.0/ > > Enjoy, > - -Barry > > Barry Warsaw > [EMAIL PROTECTED] > Python 2.6/3.0 Release Manager > (on behalf of the entire python-dev team) > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (Darwin) > > iQCVAwUBSTc3pXEjvBPtnXfVAQI69wP/dPHh8IL3GxziEV9QzlveKG+KyZb2X16x > fxJnTCiXAbiAhT5C+m43OEnbF1PJgMDKtcZ5b7aQb4TQ0mJxISTQh0RfLCpArmlo > tdTbzCLnh13KzB+3sUHCx+MeQNXERoWDV8hLz+4Ae71UsuUGynhtyP7ZJMJDue8j > so2gv3fOMSs= > =vkiy > -END PGP SIGNATURE- > ___ > Python-3000 mailing list > [EMAIL PROTECTED] > http://mail.python.org/mailman/listinfo/python-3000 > Unsubscribe: > http://mail.python.org/mailman/options/python-3000/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] RELEASED Python 3.0 final
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 3, 2008, at 9:13 PM, Dotan Cohen wrote: On this page: http://www.python.org/download/releases/3.0/ The text "This is a proeuction release" should probably read "This is a production release". It would give a better first impression :) Fixed, thanks! - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSTc/WHEjvBPtnXfVAQL8TwP+M2Ryv7WY36ICEvzGU4EzlRG/gI4MolQe cD8DJUJfQuR6INTot/t7vTcL8oDHq7q9OHbfvd3jmSwH/ZytsMz2OvJUYlKDQjwG BcQRpioprcesoU6cufSmKAUiUP+L0RTAMmT0WDbbeCzzMZRq3Humd4Zs43nL26NT uFb83Dk6yWA= =qPjn -END PGP SIGNATURE- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] RELEASED Python 3.0 final
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 3, 2008, at 9:19 PM, Guido van Rossum wrote: Thanks so much for seeing this one through, Barry and co! Champagne!!! Now if only I could go on vacation. :) - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSTc/gXEjvBPtnXfVAQKZGgP/Y41JSlU6bQlGQKQmrjxv2jUWf2AWDLSu 4HG45m5plX/r6z1bZlxdqvpVqVRGgInoe+uw96WEgjW+F5NomU4ZKQ+YVOZFjkJY izAWQllxZRkErdIBq158DOKTTyiJpUpRnGvwx2J67/pIBGLfFLZ+yPAu+4jT4fJ+ qFq/oGKCKIY= =wiBX -END PGP SIGNATURE- ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] RELEASED Python 3.0 final
On Dec 3, 2008, at 7:51 PM, Barry Warsaw wrote: On behalf of the Python development team and the Python community, I am happy to announce the release of Python 3.0 final. Props to all the folks whose hard work made this possible! You guys rock! -- Ed Leafe ___ Python-Dev mailing list [email protected] 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.3 and 2.4.6 release schedule
I would like to create 2.5.3 and 2.4.6 release candidates next week, December 12, and final releases on December 19. If there are any open issues that you think need to be considered, please create a bug in the bug tracker, mark it as release blocker, and label it with version 2.5.3 (or 2.4). Of course, a number of such issues are already in the tracker, some already being worked on. Remember: 2.5.3 will be the last bug fix release for Python 2.5; afterwards, only security patches will be accepted for the 2.5 branch. The 2.4 branch is already in that state (the 2.3 branch is not maintained anymore; 2.4 security patches will be produced until November 2009). Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Merging mailing lists
I would like to merge mailing lists, now that the design and first implementation of Python 3000 is complete. In particular, I would like to merge the python-3000 mailing list back into python-dev, and the python-3000-checkins mailing list back into python-checkins. The rationale is to simplify usage of the lists, and to avoid cross-postings. To implement this, all subscribers of the 3000 mailing lists would be added to the trunk mailing lists (avoiding duplicates, of course), and all automated messages going to python-3000-checkins would then be directed to the trunk lists. The 3000 mailing lists would change into read-only mode (i.e. primarily leaving the archives behind). Any objections? Regards, Martin ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
