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 robertwb
Recipients Alexander.Belopolsky, akitada, christian.heimes, josm, loewis, mark.dickinson, rhettinger, robertwb, zanella
Date 2010-05-01.19:02:39
SpamBayes Score 0.003154637
Marked as misclassified No
Message-id <>
Thank you Alexander. Yes, there is still an issue for large operands, and the attached patch does fix it. Floats are explicitly checked for and rejected by PyArg_ParseTuple for the "l" format (as called by builtin_range) so to preserve this behavior we can explicitly check in the argument parsing of handle_range_longs as well.

This all goes away in Py3 due to the unification of int and long. (And I agree that using __index__ rather than __int__ fits better there).
Date User Action Args
2010-05-01 19:02:41robertwbsetrecipients: + robertwb, loewis, rhettinger, mark.dickinson, christian.heimes, josm, zanella, akitada, Alexander.Belopolsky
2010-05-01 19:02:41robertwbsetmessageid: <>
2010-05-01 19:02:40robertwblinkissue1533 messages
2010-05-01 19:02:40robertwbcreate