Martin v. Löwis <[email protected]> added the comment: 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. ---------- _______________________________________ Python tracker <[email protected]> <http://bugs.python.org/issue14923> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
