[Python-Dev] Cherry-pick between Python 3.4 RC2 and final?

[Victor Stinner]

Hi,

2014-03-03 22:38 GMT+01:00 Nick Coghlan <ncoghlan at gmail.com>:
> Related question - have you decided yet whether or not to do an rc3?

I take a look at current release blocker issues for Python 3.4. I saw
bugfixes (ex: upgrade SQLite from 3.8.3 to 3.8.3.1) but also fixes for
regressions between Python 3.4rc2 and Python 3.4rc1, especially about
pip on Windows.

It looks like the Windows installer *and* pip are currently broken on
Windows with Python 3.4rc2. It would be sad to release Python 3.4 with
pip broken (on Windows) since it was announced (*) that Python 3.4
finally fixes the "pip bootstrap" issue, and users may expect this
feature.

If we fix the Windows installer and pip on Windows, it would be safer
to have a RC3 because I don't know how to test Windows installer and I
don't want to learn how to do that.

Note: There are also requested changes in OS X installer (upgrade SQLite).

IMO a perfect final version is exactly the same than the last RC
except that the version changed. Here I see a long list of cherry-pick
issues...

@Larry: What do you think of a RC3 for March 16th, and a final release
one week later (March 23th)? (Or maybe a RC3 for this week-end if you
have some free time :-))

(*) Read for example https://lwn.net/Articles/570471/ "Rationalizing
Python packaging"

Victor