Home Original page

[Python-Dev] Octal literals

Bengt Richter bokr at oz.net
Mon Feb 6 06:33:57 CET 2006 
On Sun, 5 Feb 2006 18:08:58 -0800, Guido van Rossum <guido at python.org> wrote:

>On 2/5/06, Bengt Richter <bokr at oz.net> wrote:
>> On Sun, 05 Feb 2006 09:38:35 -0800, Josiah Carlson <jcarlson at uci.edu> 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
More information about the Python-Dev mailing list