➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mark.dickinson
Recipients alexhsamuel, benjamin.peterson, mark.dickinson, nascheme
Date 2010-06-17.12:40:17
SpamBayes Score 0.0044009034
Marked as misclassified No
Message-id <1276778419.67.0.700224218468.issue9011@psf.upfronthosting.co.za>
In-reply-to
Content 
Fixed in r82043 (py3k) and r82044 (release31-maint), simply by removing the relevant 'if' block.

For 2.x, Antoine (on IRC) pointed out that there might well be third party code that depends on -0x80000000 being an int rather than a long (32-bit machine), so changing that behaviour could cause breakage.

Can anyone propose a fix that doesn't change behaviour?
History
Date User Action Args
2010-06-17 12:40:19mark.dickinsonsetrecipients: + mark.dickinson, nascheme, benjamin.peterson, alexhsamuel
2010-06-17 12:40:19mark.dickinsonsetmessageid: <1276778419.67.0.700224218468.issue9011@psf.upfronthosting.co.za>
2010-06-17 12:40:18mark.dickinsonlinkissue9011 messages
2010-06-17 12:40:17mark.dickinsoncreate