Sorry for the late reply; it's been kinda busy around here.
If there are places left, I'll definitely be there at the summit.
Congratulations on your impending doom! (And sorry to hear that you
might not be there in Florence.)
On Sat, Apr 16, 2011 at 3:50 PM, Michael Foord <michael(a)python.org> wrote:
> Hello all,
> This is an invite to all core-python developers, and developers of
> alternative implementations, to attend the Python Language Summit at
> EuroPython. The summit will be on June 19th and EuroPython this year will be
> held at the beautiful city of Florence in Italy.
> If you are not a core-Python developer but would like to attend then please
> email me privately and I will let you know if spaces are available. If you
> are a core developer, or you have received a direct invitation, then please
> respond by private email to let me know if you are able to attend. 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 appropriate breaks.
> Like previous language summits it is an opportunity to discuss topics like,
> Python 3 adoption, PEPs and changes for Python 3.3, the future of Python
> 2.7, documentation, package index, web site, etc.
> If you have topics you'd like to discuss at the language summit please let
> me know.
> Volunteers for taking notes at the language summit, for posting to
> Python-dev and the Python Insiders blog after the event, would be much
> All the best,
> Michael Foord
> N.B. Due to my impending doom (oops, I mean impending fatherhood) I am not
> yet 100% certain I will be able to attend. If I can't I will arrange for
> someone else to chair.
> May you do good and not evil
> May you find forgiveness for yourself and forgive others
> May you share freely, never taking more than you give.
> -- the sqlite blessing http://www.sqlite.org/different.html
I actually made the 2.6.7rc1 release and pushed it out to dinsdale, but Martin
tells me that the hg and svn branches for 2.6 are not synchronized. Dang, I
should have checked that first.
I'm going to hold off announcing the availability of 2.6.7rc1 until I have
some time to synchronize the branches, and possibly decide whether to do the
actual release from hg or svn. Issue 12024 is the release blocker for this.
It might mean doing an rc2, but I probably won't get to that for another
week. Which I think is okay, because this is basically a self-imposed
Service announcement from your friendly release manager:
Since 3.2.1 is the first release from Mercurial, I'm likely going to need
extra time figure out the best process, and to go through PEP 101 and fix
it (XXX what do we do with the SVN instructions, which are still valid
Therefore, I've decided to go through the process this weekend already,
in order not to screw up the only rc for 3.2.1 (planned for next weekend).
And while I'm at it, I figure I can make the result public in any case, so
there will be a 3.2.1 beta 1.
Since I'm going to work in a separate release branch (clone), there won't
be freezes anymore and the additional release won't disturb development
during the weekend.
Martin, Ned: I would say it's not mandatory for the beta release to have
binaries, but you might want to test out your toolchains against the new
I'd like to make a Python 2.6.7 release candidate this Friday, May 6, with a
final release scheduled for May 20. I've put these dates on the Python
Release Schedule calendar.
This will be a source-only security release. I see no release blockers for
Python 2.6, so if you know of anything that must go into 2.6.7, please be sure
there is a tracker issue for it, that 2.6 is marked as being affected, and
with a release blocker priority.
On May 1, 2011, at 10:57 AM, Georg Brandl wrote:
> I'd like to release Python 3.2.1 on May 21, with a release candidate
> on May 14. Please bring any issues you think need to be fixed in it
> to my attention by assigning "release blocker" status in the tracker.
Thanks to http://www.python.org/dev/daily-dmg/ , I've been able
to work off of the head every day. Python 3.2.1 is in pretty good shape :-)