On Mon, Feb 6, 2012 at 2:02 PM, Michael Foord <mich...@voidspace.org.uk> wrote: > > On 6 Feb 2012, at 21:55, Brett Cannon wrote: > >> >> >> On Tue, Jan 10, 2012 at 08:04, Michael Foord <mich...@voidspace.org.uk> >> wrote: >> Hello Python Committers, >> >> As usual we will hold a Python Language Summit before the PyCon US >> conference. >> >> The language summit will be in the conference hotel, to discuss the ongoing >> development of the Python language. It will be held on the *Wednesday* >> before the conference (Wednesday 7th March), a change from previous years. >> >> The language summit is an invite only event. All Python core developers, >> plus selected others, are invited. If you would like to attend, for all or >> part of the day, please respond off list to me so I can keep a track of >> numbers. >> >> If you have topics you would like to see on the agenda please also let me >> know. >> >> With the importlib bootstrap work close to being done (just minor >> compatibility issues at this point), it probably wouldn't hurt to discuss >> what exactly needs to be done to allow the merging of the code to happen (if >> any). > > > Added. We have a healthier looking list of topics to discuss now. > > > Which namespace PEP (382 or 402, if either) is to be accepted for 3.3. Barry > Warsaw > > How can the PSF help alternate implementations. Steve Holden > > Experimental packages in the standard library. > > Splitting out standard library into a separate repo. Barry Warsaw > > Proposed changes to the release cycle (and LTS releases). > > What we can do to get speed.python.org going. And all of this plays into what > the other VMs need from CPython for Python 3 support to be easier. Brett > Cannon > > What can be done in Python 3 to make web development easier. > > virtualenv-like functionality in Python. Vinay Sajip and Carl Meyer > > importlib bootstrap -- Brett >
Could we collect links to some background reading (whether they be mailing list threads, blog posts, + posts, etc) on each of the topics (wiki page?) and send that out several days before the meeting so that more of us can be up to speed beforehand? For example I'm not up on the current issues impacting web development under Python 3 and I doubt I'm the only one (or if I am, yay me!). -gps _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
