-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If a patch in 3.2 is not applicable in 3.3, a null merge should be
done. If not, next developer tring to merge will find some other
unrelated code to merge, and she doesn't have the context knowledge to
know what to do :-).
In this case, I merged
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/04/11 22:48, Antoine Pitrou wrote:
On Tue, 19 Apr 2011 15:20:13 -0400
Doug Hellmann doug.hellm...@gmail.com wrote:
Victor, if you want to post the call for support to Python Insider, let me
know off list and I will set you up with access.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30/03/11 18:27, Antoine Pitrou wrote:
On Wed, 30 Mar 2011 18:11:53 +0200
Victor Stinner victor.stin...@haypocalc.com wrote:
Le mercredi 30 mars 2011 à 17:59 +0200, Victor Stinner a écrit :
I'm testing my faulthandler repository on the custom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/04/11 00:37, Nick Coghlan wrote:
However, the combination of running on Ubuntu 11.04+ and need to
build security patched version of old Python seems unlikely.
Well, I, for one, have Python 2.3, 2.4, 2.5, 2.6, 2.7, 3.1 and 3.2
installed in my
