469,935 Members | 1,924 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,935 developers. It's quick & easy.

Re: Python "is" behavior

On Fri, 20 Jun 2008 09:31:57 -0700 (PDT), mi*************@gmail.com wrote:
>I am not certain why this is the case, but...
>>>a = 256
b = 256
a is b
True
>>>a = 257
b = 257
a is b
False

Can anyone explain this further? Why does it happen? 8-bit integer
differences?
http://mail.python.org/pipermail/pyt...er/113994.html

Jean-Paul
Jun 27 '08 #1
3 1223
On Jun 20, 9:38*am, Jean-Paul Calderone <exar...@divmod.comwrote:
On Fri, 20 Jun 2008 09:31:57 -0700 (PDT), michalis.avr...@gmail.com wrote:
I am not certain why this is the case, but...
>>a = 256
b = 256
a is b
True
>>a = 257
b = 257
a is b
False
Can anyone explain this further? Why does it happen? 8-bit integer
differences?

http://mail.python.org/pipermail/pyt...er/113994.html

Jean-Paul
Thank you for this Jean-Paul. I did know about the identity of
objects, but my curiosity is based on the 256 number. Are the 2^8
integers cached due to the internal loops, or is there any other
specific reason? Is this something that can be controlled?
Jun 27 '08 #2
mi*************@gmail.com wrote:
On Jun 20, 9:38 am, Jean-Paul Calderone <exar...@divmod.comwrote:
>On Fri, 20 Jun 2008 09:31:57 -0700 (PDT), michalis.avr...@gmail.com wrote:
>>I am not certain why this is the case, but...

>a = 256
>b = 256
>a is b
>>
True

>a = 257
>b = 257
>a is b
>>
False

Can anyone explain this further? Why does it happen? 8-bit integer
differences?
http://mail.python.org/pipermail/pyt...er/113994.html

Jean-Paul

Thank you for this Jean-Paul. I did know about the identity of
objects, but my curiosity is based on the 256 number. Are the 2^8
integers cached due to the internal loops, or is there any other
specific reason? Is this something that can be controlled?
Python provides no way to change that number, but of course you can
always fiddle with the source code and recompile. The actual value is
a trade off (like any caching scheme) of cache-space versus efficiency
gains. The value has changed at least once in recent versions of Python.

Gary Herron
--
http://mail.python.org/mailman/listinfo/python-list
Jun 27 '08 #3
Lie
On Jun 21, 2:14*am, Gary Herron <gher...@islandtraining.comwrote:
michalis.avr...@gmail.com wrote:
On Jun 20, 9:38 am, Jean-Paul Calderone <exar...@divmod.comwrote:
On Fri, 20 Jun 2008 09:31:57 -0700 (PDT), michalis.avr...@gmail.com wrote:
>I am not certain why this is the case, but...
>>>>a = 256
b = 256
a is b
>True
>>>>a = 257
b = 257
a is b
>False
>Can anyone explain this further? Why does it happen? 8-bit integer
differences?
>http://mail.python.org/pipermail/pyt...er/113994.html
Jean-Paul
Thank you for this Jean-Paul. I did know about the identity of
objects, but my curiosity is based on the 256 number. Are the 2^8
integers cached due to the internal loops, or is there any other
specific reason? Is this something that can be controlled?

Python provides no way to change that number, but of course you can
always fiddle with the source code and recompile. * The actual value is
a trade off (like any caching scheme) of cache-space versus efficiency
gains. * The value has changed at least once in recent versions of Python.
And if your code breaks because of this, don't whine, 'cause you've
already been warned not to rely on it. Exactly the same arguments with
other people that is/going to whine because they break the
encapsulation.
Jun 27 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

36 posts views Thread by Armin Rigo | last post: by
114 posts views Thread by Maurice LING | last post: by
20 posts views Thread by Wayne Sutton | last post: by
9 posts views Thread by Lonnie Princehouse | last post: by
92 posts views Thread by ureuffyrtu955 | last post: by
4 posts views Thread by michalis.avraam | last post: by
reply views Thread by Jean-Paul Calderone | last post: by
8 posts views Thread by ssecorp | last post: by
2 posts views Thread by chenxinleo | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.