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 amk@amk.ca 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.
On Wed, Dec 3, 2008 at 4:31 PM, A.M. Kuchling amk@amk.ca 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-cu...
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 Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/ziade.tarek%40gmail.com
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.
On Wed, Dec 3, 2008 at 9:44 PM, Nick Coghlan ncoghlan@gmail.com 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
On Wed, Dec 3, 2008 at 10:31 AM, A.M. Kuchling amk@amk.ca wrote:
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.
I would like to champion this one.
-Frank
On Thu, Dec 4, 2008 at 12:05, Frank Wierzbicki fwierzbicki@gmail.com wrote:
On Wed, Dec 3, 2008 at 10:31 AM, A.M. Kuchling amk@amk.ca wrote:
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.
I would like to champion this one.
I told AMK this a while back, but might as well make it more public; I am up for chairing as well.
-Brett
On Thu, Dec 4, 2008 at 3:16 PM, Brett Cannon brett@python.org wrote:
On Thu, Dec 4, 2008 at 12:05, Frank Wierzbicki fwierzbicki@gmail.com wrote:
On Wed, Dec 3, 2008 at 10:31 AM, A.M. Kuchling amk@amk.ca wrote:
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.
I would like to champion this one.
I told AMK this a while back, but might as well make it more public; I am up for chairing as well.
Brett,
Are you saying you've already called the cross-implementation champion role? If so I'm happy to defer or co-chair.
-Frank
On Thu, Dec 4, 2008 at 17:02, Frank Wierzbicki fwierzbicki@gmail.com wrote:
On Thu, Dec 4, 2008 at 3:16 PM, Brett Cannon brett@python.org wrote:
On Thu, Dec 4, 2008 at 12:05, Frank Wierzbicki fwierzbicki@gmail.com wrote:
On Wed, Dec 3, 2008 at 10:31 AM, A.M. Kuchling amk@amk.ca wrote:
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.
I would like to champion this one.
I told AMK this a while back, but might as well make it more public; I am up for chairing as well.
Brett,
Are you saying you've already called the cross-implementation champion role?
No, I am saying I had told AMK I was interested in championing the session. He chose you, and that's that. One less thing for me to worry about. =)
If so I'm happy to defer or co-chair.
Your call. I will definitely be there representing CPython as best as I can, so I will be making noise regardless of whether I am standing in front of the room or not.
-Brett
On Sat, Dec 06, 2008 at 02:42:38PM -0800, Brett Cannon wrote:
No, I am saying I had told AMK I was interested in championing the session. He chose you, and that's that. One less thing for me to worry about. =)
Brett, I actually think you'd be a good champion for the 11AM transition-planning session. As a reminder, the topics came up with were:
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?
(Possibly this is too much material for one session, and something will have to be pruned.)
--amk
On Mon, Dec 8, 2008 at 18:53, A.M. Kuchling amk@amk.ca wrote:
On Sat, Dec 06, 2008 at 02:42:38PM -0800, Brett Cannon wrote:
No, I am saying I had told AMK I was interested in championing the session. He chose you, and that's that. One less thing for me to worry about. =)
Brett, I actually think you'd be a good champion for the 11AM transition-planning session.
OK, so I guess I do have one more thing to worry about. =) I'd be happy to do that session.
As a reminder, the topics came up with were:
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?
Probably the last two will be wishy-washy in terms of whether they will be reached.
-Brett
On Mon, Dec 8, 2008 at 10:31 PM, Brett Cannon brett@python.org wrote:
On Mon, Dec 8, 2008 at 18:53, A.M. Kuchling amk@amk.ca wrote:
On Sat, Dec 06, 2008 at 02:42:38PM -0800, Brett Cannon wrote:
No, I am saying I had told AMK I was interested in championing the session. He chose you, and that's that. One less thing for me to worry about. =)
Brett, I actually think you'd be a good champion for the 11AM transition-planning session.
OK, so I guess I do have one more thing to worry about. =) I'd be happy to do that session.
Sounds good, and I'm still happy to do the other session even with all of the heckling :)
-Frank
participants (5)
-
A.M. Kuchling -
Brett Cannon -
Frank Wierzbicki -
Nick Coghlan -
Tarek Ziadé