[Python-Dev] Merging changes before beta

Amaury Forgeot d'Arc amauryfa at gmail.com
Tue Jun 17 21:44:45 CEST 2008


I am in the process of merging changes from trunk to the py3k branch.
(If somebody else is already doing it, please tell me quickly!)

IMO it would be better to have the beta versions in sync;
the 2.6->3.0 migration should not be a regression!

I will integrate the changes that are either simple, or that I can understand,
or have unit tests.

The changes I will skip are (for the moment):

- r64114 (gregory.p.smith): a bunch of checks for integer overflows,
contributed by Google.
This change has many conflicts, I will do it later.

- r63828 (mark.hammond): Fix bdist_wininst --user-access-control for win2k
For this it is necessary to recompile the various wininst-*.exe,
and not all my compilers have the necessary headers or libraries.

- r63955 (ronald.oussoren): MacOS X: Enable 4-way universal builds
I may try the merge, but without any way to test the result.
OTOH, I could go and trust the buildbots.

- 64062,64068-64069,64080 (josiah.carlson): Asynchat
I may give a try, but it will be tricky. And I don't even know how
asynchat works
(I just remember it was hard to get it right for python 3.0)

- 63207,63210,63218,63403,63469,63537,63597-63598,63601,63604,63617-63618,
63714,63718,63742,63745,63799 (jesus.cea, gregory.p.smith): bsddb module
This is a important list of changes, and may require heavy adaptations
to the code.
issue2887 has been filed for this task.

Do you think these tasks should be considered as Release Blockers?
Beta1 is close...

Amaury Forgeot d'Arc

More information about the Python-Dev mailing list