Robert Bradshaw <rober...@math.washington.edu> added the comment: 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). ---------- Added file: http://bugs.python.org/file17169/bltinmodule2.diff _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1533> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
