On Sun, 5 Feb 2006 18:08:58 -0800, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>On 2/5/06, Bengt Richter <[EMAIL PROTECTED]> wrote: >> On Sun, 05 Feb 2006 09:38:35 -0800, Josiah Carlson <[EMAIL PROTECTED]> wrote: >> >1. If your Python code distinguishes between ints and longs, it has a >> >bug. >> Are you just lecturing me personally (in which case off list would be more >> appropriate), >> or do you include the authors of the 17 files I count under <some >> prefix>/Lib that have >> isinstance(<something>, int) in them? > >Josiah is correct, and those modules all have bugs. > It seems I stand incontestably corrected. Sorry, both ways ;-/ Perhaps I missed a py3k assumption in this thread (where I see in the PEP that "Remove distinction between int and long types" is core item number one)? I googled, but could not find that isinstance(<something>,int) was slated for deprecation, so I assumed that Josiah's absolute statement "1. ..." (above) could not be absolutely true, at least in the "has" (present) tense that he used. Is PEP 237 phase C to be implemented sooner than py3k, making isinstance(<something>, int) a transparently distinction-hiding alias for isinstance(<something>, integer), or outright illegal? IOW, will isinstance(<something>, int) be _guaranteed_ to be a bug, thus requiring code change? If so, when? Regards, Bengt Richter _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
