python grmph

apparently small ints are Special

>>> a = 256
>>> b = 256
>>> a == b
True
>>> a is b
True
>>> a = 257
>>> b = 257
>>> a == b
True
>>> a is b
False

This entry was posted on Friday, May 27th, 2011 at 7:36 pm and is filed under blodgett, cod. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

4 Responses to “python grmph”

  1. doik says:
    May 28, 2011 at 8:53 pm

    that sort of even makes sense maybe. this does not:

    >>> a = -5

    >>> b = -5

    >>> a is b

    True

    >>> a = -6

    >>> b = -6

    >>> a is b

    False

    >>> a = -6; b = -6

    >>> a is b

    True

  2. cakesniffer says:
    May 29, 2011 at 4:01 pm

    Does sort of: it’s caching immutable small int objects and handing you back a reference to an existing one rather than creating loads of separate objects for every “1”. Then it pre-fills the cache with -5..255 which are presumably the most common.

  3. cakesniffer says:
    May 29, 2011 at 7:41 pm

    On second thoughts, that isn’t actually supported by the above example. Maybe it doesn’t make sense.

  4. blodgett says:
    May 30, 2011 at 12:01 pm

    transparency not python strong suit rly

Leave a Reply