We will be holding another Python language summit as part of PyCon 2011
in Atlanta. The summit will be on Thursday March 10th, the second day of
the tutorials and the day before the conference proper begins.
All python-committers are invited (if you have attended in previous
years you will receive another copy of this invitation). If you intend
to attend, or think it is likely that you will attend, please reply and
let me know as soon as possible to help with venue planning. A maybe is
fine, you can always change your mind later. Attending for only part of
the day is fine. We expect the summit to run from 10am - 4pm with
We will also be inviting contributors to alternative implementations of
Python, and select Python community members. Again, having an idea of
the number of attendees help us to decide how many of these we can invite.
If you are giving a tutorial and would also like to attend the language
summit you will need to talk to the tutorial organisers and let them
know that you won't be available on the Thursday.
As in previous years we are also running a VM summit, on Wednesday March
9th. This is by invite only, with no general invitation to
python-committers. Invites have already gone out, but if you would like
to be included please email me and (space permitting) I will add you.
If you have suggestions of people you think should be invited to the
language summit then feel free to pass them onto me.
Details of the language summit are below.
What is it?
The Python Language Summit is an invitation-only event for the
developers of Python implementations (CPython, IronPython, Jython,
Parrot, PyPy, etc.) to share information, discuss our shared problems
and hopefully solve them.
These issues might be related to the language itself, the standard
library, the development process, Python 3.x and 2.x, the
documentation, package index, web site, etc. The Summit will focus on
discussion more than on presentations; the planned program is included
at the bottom of this message. We're currently planning for 50-60
people to attend the Summit.
The Language Summit is being organized in conjunction with PyCon 2011,
with support from the Python Software Foundation. This is the fourth
Previous summits were held at PyCon 2009 & 2010 and EuroPython 2010.
Where is it?
The Language Summit will be at the Hyatt Atlanta Regency Hotel
( http://atlantaregency.hyatt.com/hyatt/hotels/index.jsp ), the same hotel
where the conference is being held. Thursday March 10 is the day before
begins, and is also the second day of the PyCon tutorials.
The summit will be from 10am - 4pm and is likely to be in the Courtland or
Dunwoody rooms. Further details will be emailed to attendees before the
What is required?
Attending the Summit is free. You are responsible for your travel and
If you wish to attend PyCon, you must still register and pay for
PyCon. Note that you don't have to stay for PyCon if you're only
interested in the Language Summit.
As it does every year, PyCon will be offering financial assistance to
people who are unable to attend the conference otherwise. I am not on
the financial-aid committee and can't guarantee anything, but language
summit attendees would stand a very good chance of receiving some aid.
See http://us.pycon.org/2010/registration/financial-aid/ for more
information about financial aid. (This is the 2010 page, registration
for 2011 has not yet opened. Procedures for applying for financial
aid are likely to be the same as 2010.)
What do I need to do?
If you would like to attend the summit, or would like a slot to be
reserved for you, then please reply to this email (off-list). We only
have space for 60 attendees so it is important we know who is attending.
Note that the summit proceedings may be recorded and made publicly
I look forward to seeing you and working with you at the Summit.
Coordinator, Python Language Summit
p.s. The sessions have not been finally decided. Suggestions for topics
of discussion will be gratefully received. Once I have a session
outlines I will post them on this list. Bonus points for reading this
far down the email by the way...
READ CAREFULLY. By accepting and reading this email you agree,
on behalf of your employer, to release me from all obligations
and waivers arising from any and all NON-NEGOTIATED agreements,
licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap,
confidentiality, non-disclosure, non-compete and acceptable use
policies (”BOGUS AGREEMENTS”) that I have entered into with your
employer, its partners, licensors, agents and assigns, in
perpetuity, without prejudice to my ongoing rights and privileges.
You further represent that you have the authority to release me
from any BOGUS AGREEMENTS on behalf of your employer.
All ssh repos can now be accessed by using ssh://email@example.com/repo
instead of ssh://firstname.lastname@example.org/repos/repo. While the old way should
continue to work, the new address should be considered preferable.
Now that I've started work at Google, I'd like to add new ssh keys so that I
can commit from my work desktop and laptop. I hope that 20%-time will allow
me to contribute to Python on a somewhat more regular basis than my previous
sporadic bursts of activity. :-)
-----BEGIN PGP SIGNED MESSAGE-----
On behalf of the Python development team, I'm happy to announce the
fourth and (this time really) final alpha preview release of Python 3.2.
Python 3.2 is a continuation of the efforts to improve and stabilize the
Python 3.x line. Since the final release of Python 2.7, the 2.x line
will only receive bugfixes, and new features are developed for 3.x only.
Since PEP 3003, the Moratorium on Language Changes, is in effect, there
are no changes in Python's syntax and built-in types in Python 3.2.
Development efforts concentrated on the standard library and support for
porting code to Python 3. Highlights are:
* numerous improvements to the unittest module
* PEP 3147, support for .pyc repository directories
* PEP 3149, support for version tagged dynamic libraries
* an overhauled GIL implementation that reduces contention
* many consistency and behavior fixes for numeric operations
* countless fixes regarding string/unicode issues; among them full
support for a bytes environment (filenames, environment variables)
* a sysconfig module to access configuration information
* a pure-Python implementation of the datetime module
* additions to the shutil module, among them archive file support
* improvements to pdb, the Python debugger
For an extensive list of changes in 3.2, see Misc/NEWS in the Python
To download Python 3.2 visit:
3.2 documentation can be found at:
Please consider trying Python 3.2 with your code and reporting any bugs
you may notice to:
Georg Brandl, Release Manager
georg at python.org
(on behalf of the entire python-dev team and 3.2's contributors)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
-----END PGP SIGNATURE-----