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 loewis
Recipients Arfrever, ezio.melotti, janssen, jcea, loewis, mark.dickinson, ned.deily, pitrou, python-dev, ronaldoussoren, serhiy.storchaka, vstinner
Date 2012-05-26.10:02:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1338026530.5.0.693378684931.issue14923@psf.upfronthosting.co.za>
In-reply-to
Content
The C standard says, in 6.3.1.3/3

Otherwise [*], the new type is signed and the value cannot be represented in it; either the result is implementation-defined or an implementation-defined signal is raised.

[*]: the value cannot be exactly converted, and the target type is not unsigned.

We shouldn't be using unsigned->signed conversions where the source value is out of range for the signed type.
History
Date User Action Args
2012-05-26 10:02:10loewissetrecipients: + loewis, jcea, ronaldoussoren, mark.dickinson, janssen, pitrou, vstinner, ned.deily, ezio.melotti, Arfrever, python-dev, serhiy.storchaka
2012-05-26 10:02:10loewissetmessageid: <1338026530.5.0.693378684931.issue14923@psf.upfronthosting.co.za>
2012-05-26 10:02:09loewislinkissue14923 messages
2012-05-26 10:02:09loewiscreate