Paul A. added the comment:

On Sun, Nov 18, 2012 at 08:01:39PM +0000, Terry J. Reedy wrote:
> I should have added 'please try compiling 3.x to make sure it has the same 
> problem' since configure might behave differently.

I'm fairly sure I did, that was quite a few months ago, so my memory
could be faulty.  I did eventually get both of 2.6.7 and 2.7.3 built,
I really must submit my patches.  I suppose it should go against the
current 2.7 in the repo, correct?


Python tracker <>
Python-bugs-list mailing list

Reply via email to