Different object size of True and False in Python 3

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
16
down vote

favorite
2












Experimenting with magic methods (__sizeof__ in particular) on different Python objects I stumbled over the following behaviour:



Python 2.7



>>> False.__sizeof__()
24
>>> True.__sizeof__()
24


Python 3.x



>>> False.__sizeof__()
24
>>> True.__sizeof__()
28


What changed in Python 3 that makes the size of True greater than the size of False?










share|improve this question



















  • 2




    dir is totally irrelevant.
    – juanpa.arrivillaga
    7 hours ago






  • 3




    Related, the same behavior appears for 0 vs 1
    – user3483203
    7 hours ago










  • @juanpa.arrivillaga can you qualify that? If dir is irrelevant in understanding this, what is?
    – roganjosh
    7 hours ago






  • 2




    Because dir returns a lot of things that have nothing to do with what sys.sizeof returns. Note, dir([1,2,3,4,5]) == dir() but sys.getsizeof([1,2,3,4,5,]) != sys.getsizeof()
    – juanpa.arrivillaga
    7 hours ago






  • 1




    @roganjosh and just in general, dir will give you every attribute accessible from an object, but you don't care about that, so for example, when you ask about the size of an object you generally don't want to include all the methods that belong to various classes that it has access to, do you?
    – juanpa.arrivillaga
    7 hours ago















up vote
16
down vote

favorite
2












Experimenting with magic methods (__sizeof__ in particular) on different Python objects I stumbled over the following behaviour:



Python 2.7



>>> False.__sizeof__()
24
>>> True.__sizeof__()
24


Python 3.x



>>> False.__sizeof__()
24
>>> True.__sizeof__()
28


What changed in Python 3 that makes the size of True greater than the size of False?










share|improve this question



















  • 2




    dir is totally irrelevant.
    – juanpa.arrivillaga
    7 hours ago






  • 3




    Related, the same behavior appears for 0 vs 1
    – user3483203
    7 hours ago










  • @juanpa.arrivillaga can you qualify that? If dir is irrelevant in understanding this, what is?
    – roganjosh
    7 hours ago






  • 2




    Because dir returns a lot of things that have nothing to do with what sys.sizeof returns. Note, dir([1,2,3,4,5]) == dir() but sys.getsizeof([1,2,3,4,5,]) != sys.getsizeof()
    – juanpa.arrivillaga
    7 hours ago






  • 1




    @roganjosh and just in general, dir will give you every attribute accessible from an object, but you don't care about that, so for example, when you ask about the size of an object you generally don't want to include all the methods that belong to various classes that it has access to, do you?
    – juanpa.arrivillaga
    7 hours ago













up vote
16
down vote

favorite
2









up vote
16
down vote

favorite
2






2





Experimenting with magic methods (__sizeof__ in particular) on different Python objects I stumbled over the following behaviour:



Python 2.7



>>> False.__sizeof__()
24
>>> True.__sizeof__()
24


Python 3.x



>>> False.__sizeof__()
24
>>> True.__sizeof__()
28


What changed in Python 3 that makes the size of True greater than the size of False?










share|improve this question















Experimenting with magic methods (__sizeof__ in particular) on different Python objects I stumbled over the following behaviour:



Python 2.7



>>> False.__sizeof__()
24
>>> True.__sizeof__()
24


Python 3.x



>>> False.__sizeof__()
24
>>> True.__sizeof__()
28


What changed in Python 3 that makes the size of True greater than the size of False?







python python-3.x python-2.7 cpython python-internals






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 26 mins ago









Peter Mortensen

13.2k1983111




13.2k1983111










asked 7 hours ago









Simon Fromme

1,327721




1,327721







  • 2




    dir is totally irrelevant.
    – juanpa.arrivillaga
    7 hours ago






  • 3




    Related, the same behavior appears for 0 vs 1
    – user3483203
    7 hours ago










  • @juanpa.arrivillaga can you qualify that? If dir is irrelevant in understanding this, what is?
    – roganjosh
    7 hours ago






  • 2




    Because dir returns a lot of things that have nothing to do with what sys.sizeof returns. Note, dir([1,2,3,4,5]) == dir() but sys.getsizeof([1,2,3,4,5,]) != sys.getsizeof()
    – juanpa.arrivillaga
    7 hours ago






  • 1




    @roganjosh and just in general, dir will give you every attribute accessible from an object, but you don't care about that, so for example, when you ask about the size of an object you generally don't want to include all the methods that belong to various classes that it has access to, do you?
    – juanpa.arrivillaga
    7 hours ago













  • 2




    dir is totally irrelevant.
    – juanpa.arrivillaga
    7 hours ago






  • 3




    Related, the same behavior appears for 0 vs 1
    – user3483203
    7 hours ago










  • @juanpa.arrivillaga can you qualify that? If dir is irrelevant in understanding this, what is?
    – roganjosh
    7 hours ago






  • 2




    Because dir returns a lot of things that have nothing to do with what sys.sizeof returns. Note, dir([1,2,3,4,5]) == dir() but sys.getsizeof([1,2,3,4,5,]) != sys.getsizeof()
    – juanpa.arrivillaga
    7 hours ago






  • 1




    @roganjosh and just in general, dir will give you every attribute accessible from an object, but you don't care about that, so for example, when you ask about the size of an object you generally don't want to include all the methods that belong to various classes that it has access to, do you?
    – juanpa.arrivillaga
    7 hours ago








2




2




dir is totally irrelevant.
– juanpa.arrivillaga
7 hours ago




dir is totally irrelevant.
– juanpa.arrivillaga
7 hours ago




3




3




Related, the same behavior appears for 0 vs 1
– user3483203
7 hours ago




Related, the same behavior appears for 0 vs 1
– user3483203
7 hours ago












@juanpa.arrivillaga can you qualify that? If dir is irrelevant in understanding this, what is?
– roganjosh
7 hours ago




@juanpa.arrivillaga can you qualify that? If dir is irrelevant in understanding this, what is?
– roganjosh
7 hours ago




2




2




Because dir returns a lot of things that have nothing to do with what sys.sizeof returns. Note, dir([1,2,3,4,5]) == dir() but sys.getsizeof([1,2,3,4,5,]) != sys.getsizeof()
– juanpa.arrivillaga
7 hours ago




Because dir returns a lot of things that have nothing to do with what sys.sizeof returns. Note, dir([1,2,3,4,5]) == dir() but sys.getsizeof([1,2,3,4,5,]) != sys.getsizeof()
– juanpa.arrivillaga
7 hours ago




1




1




@roganjosh and just in general, dir will give you every attribute accessible from an object, but you don't care about that, so for example, when you ask about the size of an object you generally don't want to include all the methods that belong to various classes that it has access to, do you?
– juanpa.arrivillaga
7 hours ago





@roganjosh and just in general, dir will give you every attribute accessible from an object, but you don't care about that, so for example, when you ask about the size of an object you generally don't want to include all the methods that belong to various classes that it has access to, do you?
– juanpa.arrivillaga
7 hours ago













4 Answers
4






active

oldest

votes

















up vote
16
down vote













It is because bool is a subclass of int in both Python 2 and 3.



>>> issubclass(bool, int)
True


But the int implementation has changed.



In Python 2, int was the one that was 32 or 64 bits, depending on the system, as opposed to arbitrary-length long.



In Python 3, int is arbitrary-length - the long of Python 2 was renamed to int and the original Python 2 int dropped altogether.




In Python 2 you get the exactly same behaviour for long objects 1L and 0L:



Python 2.7.15rc1 (default, Apr 15 2018, 21:51:34) 
[GCC 7.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.getsizeof(1L)
28
>>> sys.getsizeof(0L)
24



The long/Python 3 int is a variable-length object, just like a tuple - when it is allocated, enough memory is allocated to hold all the binary digits required to represent it. The length of the variable part is stored in the object head. 0 requires no binary digits (its variable length is 0), but even 1 spills over, and requires extra digits.



I.e. 0 is represented as binary string of length 0:



<>


and 1 is represented as a 30-bit binary string:



<000000000000000000000000000001>


The default configuration in Python uses 30 bits in a uint32_t; so 2**30 - 1 still fits in 28 bytes on x86-64, and 2**30 will require 32;



2**30 - 1 will be presented as



<111111111111111111111111111111>


i.e. all 30 value bits set to 1; 2**30 will need more, and it will have internal representation



<000000000000000000000000000001000000000000000000000000000000>



As for True using 28 bytes instead of 24 - you need not worry. True is a singleton and therefore only 4 bytes are lost in total in any Python program, not 4 for every usage of True.






share|improve this answer






















  • Yep, and long objects just use no extra pointer to represent 0
    – juanpa.arrivillaga
    7 hours ago






  • 2




    @roganjosh they are the same type. That doesn't mean they have the same size. sys.getsizeof([1,2,3,4,5]) and sys.getsizeof() are not the same...
    – juanpa.arrivillaga
    7 hours ago










  • @roganjosh int objects in Python 2 were always the same size. long objects were arbitrarily-sized (like Python 3 int objects, indeed, Python 3 int objects are just Python 2 long objects)
    – juanpa.arrivillaga
    6 hours ago










  • @juanpa.arrivillaga now it makes sense to me :)
    – roganjosh
    6 hours ago

















up vote
6
down vote













Both True and False are longobjects in CPython:




struct _longobject _Py_FalseStruct = 
PyVarObject_HEAD_INIT(&PyBool_Type, 0)
0
;

struct _longobject _Py_TrueStruct =
PyVarObject_HEAD_INIT(&PyBool_Type, 1)
1
;



You thus can say that a Boolean is a subclass of a python-3.x int where True takes as value 1, and False takes as value 0. We thus make a call to PyVarObject_HEAD_INIT with as type parameter a reference to PyBool_Type and with ob_size as value 0 and 1 respectively.



Now since python-3.x, there is no long anymore: these have been merged, and the int object will, depending on the size of the number, take a different value.



If we inspect the source code of the longlobject type, we see:




/* Long integer representation.
The absolute value of a number is equal to
SUM(for i=0 through abs(ob_size)-1) ob_digit[i] * 2**(SHIFT*i)
Negative numbers are represented with ob_size < 0;
zero is represented by ob_size == 0.
In a normalized number, ob_digit[abs(ob_size)-1] (the most significant
digit) is never zero. Also, in all cases, for all valid i,
0 <= ob_digit[i] <= MASK.
The allocation function takes care of allocating extra memory
so that ob_digit[0] ... ob_digit[abs(ob_size)-1] are actually available.
CAUTION: Generic code manipulating subtypes of PyVarObject has to
aware that ints abuse ob_size's sign bit.
*/

struct _longobject
PyObject_VAR_HEAD
digit ob_digit[1];
;



To make a long story short, an _longobject can be seen as an array of "digits", but you should here see digits not as decimal digits, but as groups of bits that thus can be added, multiplied, etc.



Now as is specified in the comment, it says that:




 zero is represented by ob_size == 0.



So in case the value is zero, no digits are added, whereas for small integers (values less than 230 in CPython), it takes one digit, and so on.






share|improve this answer





























    up vote
    3
    down vote













    I haven't seen CPython code for this, but I believe this has something to do with optimization of integers in Python 3. Probably, as long was dropped, some optimizations were unified. int in Python 3 is arbitrary-sized int – the same as long was in Python 2. As bool stores in the same way as new int, it affects both.



    Interesting part:



    >>> (0).__sizeof__()
    24

    >>> (1).__sizeof__() # Here one more "block" is allocated
    28

    >>> (2**30-1).__sizeof__() # This is the maximum integer size fitting into 28
    28


    + bytes for object headers should complete the equation.






    share|improve this answer






















    • Actually, now in Python 3, int is just what Python 2 long was, it was really int that was "dropped"
      – juanpa.arrivillaga
      7 hours ago










    • Internally – absolutely true, I'm talking about names, but thx for clarification
      – Slam
      7 hours ago










    • Indeed, in CPython 3 source code, it's still longobject
      – juanpa.arrivillaga
      7 hours ago










    • It is actually deoptimization... pessimization?
      – Antti Haapala
      6 hours ago










    • It's probably not. I may be wrong, but this overhead does not cost as much as two different types + seamless cast in runtime. The truth is, you rarely operate such a huge amount of ints in normal python program to care about this extra memory. If you do – you should use something like numpy to run with ~0 overhead and have pure int32/64 – no headers, no reallocation. But overflows from time to time )
      – Slam
      6 hours ago

















    up vote
    2
    down vote













    Take a look at the cpython code for True and False



    Internally it is represented as integer



    PyTypeObject PyBool_Type = 
    PyVarObject_HEAD_INIT(&PyType_Type, 0)
    "bool",
    sizeof(struct _longobject),
    0,
    0, /* tp_dealloc */
    0, /* tp_print */
    0, /* tp_getattr */
    0, /* tp_setattr */
    0, /* tp_reserved */
    bool_repr, /* tp_repr */
    &bool_as_number, /* tp_as_number */
    0, /* tp_as_sequence */
    0, /* tp_as_mapping */
    0, /* tp_hash */
    0, /* tp_call */
    bool_repr, /* tp_str */
    0, /* tp_getattro */
    0, /* tp_setattro */
    0, /* tp_as_buffer */
    Py_TPFLAGS_DEFAULT, /* tp_flags */
    bool_doc, /* tp_doc */
    0, /* tp_traverse */
    0, /* tp_clear */
    0, /* tp_richcompare */
    0, /* tp_weaklistoffset */
    0, /* tp_iter */
    0, /* tp_iternext */
    0, /* tp_methods */
    0, /* tp_members */
    0, /* tp_getset */
    &PyLong_Type, /* tp_base */
    0, /* tp_dict */
    0, /* tp_descr_get */
    0, /* tp_descr_set */
    0, /* tp_dictoffset */
    0, /* tp_init */
    0, /* tp_alloc */
    bool_new, /* tp_new */
    ;

    /* The objects representing bool values False and True */

    struct _longobject _Py_FalseStruct =
    PyVarObject_HEAD_INIT(&PyBool_Type, 0)
    0
    ;

    struct _longobject _Py_TrueStruct = {
    PyVarObject_HEAD_INIT(&PyBool_Type, 1)
    1





    share|improve this answer






















    • I don't know why this was downvoted
      – Antti Haapala
      6 hours ago










    • I think i just was not as quick to answer properly as others :)
      – Kamil Niski
      6 hours ago










    • The answer only gets halfway there. It's represented as an integer.. yeah? And so what?
      – wim
      6 hours ago










    • @wim I don't see the need to explain it further since guys above already did great job at this. I don't want to duplicate content. Please refer to their answers.
      – Kamil Niski
      6 hours ago







    • 2




      I think so, but it's up to you. Should you wait for it to maybe get +3 and then delete you may earn a disciplined badge... :)
      – wim
      5 hours ago











    Your Answer





    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53015922%2fdifferent-object-size-of-true-and-false-in-python-3%23new-answer', 'question_page');

    );

    Post as a guest






























    4 Answers
    4






    active

    oldest

    votes








    4 Answers
    4






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    16
    down vote













    It is because bool is a subclass of int in both Python 2 and 3.



    >>> issubclass(bool, int)
    True


    But the int implementation has changed.



    In Python 2, int was the one that was 32 or 64 bits, depending on the system, as opposed to arbitrary-length long.



    In Python 3, int is arbitrary-length - the long of Python 2 was renamed to int and the original Python 2 int dropped altogether.




    In Python 2 you get the exactly same behaviour for long objects 1L and 0L:



    Python 2.7.15rc1 (default, Apr 15 2018, 21:51:34) 
    [GCC 7.3.0] on linux2
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import sys
    >>> sys.getsizeof(1L)
    28
    >>> sys.getsizeof(0L)
    24



    The long/Python 3 int is a variable-length object, just like a tuple - when it is allocated, enough memory is allocated to hold all the binary digits required to represent it. The length of the variable part is stored in the object head. 0 requires no binary digits (its variable length is 0), but even 1 spills over, and requires extra digits.



    I.e. 0 is represented as binary string of length 0:



    <>


    and 1 is represented as a 30-bit binary string:



    <000000000000000000000000000001>


    The default configuration in Python uses 30 bits in a uint32_t; so 2**30 - 1 still fits in 28 bytes on x86-64, and 2**30 will require 32;



    2**30 - 1 will be presented as



    <111111111111111111111111111111>


    i.e. all 30 value bits set to 1; 2**30 will need more, and it will have internal representation



    <000000000000000000000000000001000000000000000000000000000000>



    As for True using 28 bytes instead of 24 - you need not worry. True is a singleton and therefore only 4 bytes are lost in total in any Python program, not 4 for every usage of True.






    share|improve this answer






















    • Yep, and long objects just use no extra pointer to represent 0
      – juanpa.arrivillaga
      7 hours ago






    • 2




      @roganjosh they are the same type. That doesn't mean they have the same size. sys.getsizeof([1,2,3,4,5]) and sys.getsizeof() are not the same...
      – juanpa.arrivillaga
      7 hours ago










    • @roganjosh int objects in Python 2 were always the same size. long objects were arbitrarily-sized (like Python 3 int objects, indeed, Python 3 int objects are just Python 2 long objects)
      – juanpa.arrivillaga
      6 hours ago










    • @juanpa.arrivillaga now it makes sense to me :)
      – roganjosh
      6 hours ago














    up vote
    16
    down vote













    It is because bool is a subclass of int in both Python 2 and 3.



    >>> issubclass(bool, int)
    True


    But the int implementation has changed.



    In Python 2, int was the one that was 32 or 64 bits, depending on the system, as opposed to arbitrary-length long.



    In Python 3, int is arbitrary-length - the long of Python 2 was renamed to int and the original Python 2 int dropped altogether.




    In Python 2 you get the exactly same behaviour for long objects 1L and 0L:



    Python 2.7.15rc1 (default, Apr 15 2018, 21:51:34) 
    [GCC 7.3.0] on linux2
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import sys
    >>> sys.getsizeof(1L)
    28
    >>> sys.getsizeof(0L)
    24



    The long/Python 3 int is a variable-length object, just like a tuple - when it is allocated, enough memory is allocated to hold all the binary digits required to represent it. The length of the variable part is stored in the object head. 0 requires no binary digits (its variable length is 0), but even 1 spills over, and requires extra digits.



    I.e. 0 is represented as binary string of length 0:



    <>


    and 1 is represented as a 30-bit binary string:



    <000000000000000000000000000001>


    The default configuration in Python uses 30 bits in a uint32_t; so 2**30 - 1 still fits in 28 bytes on x86-64, and 2**30 will require 32;



    2**30 - 1 will be presented as



    <111111111111111111111111111111>


    i.e. all 30 value bits set to 1; 2**30 will need more, and it will have internal representation



    <000000000000000000000000000001000000000000000000000000000000>



    As for True using 28 bytes instead of 24 - you need not worry. True is a singleton and therefore only 4 bytes are lost in total in any Python program, not 4 for every usage of True.






    share|improve this answer






















    • Yep, and long objects just use no extra pointer to represent 0
      – juanpa.arrivillaga
      7 hours ago






    • 2




      @roganjosh they are the same type. That doesn't mean they have the same size. sys.getsizeof([1,2,3,4,5]) and sys.getsizeof() are not the same...
      – juanpa.arrivillaga
      7 hours ago










    • @roganjosh int objects in Python 2 were always the same size. long objects were arbitrarily-sized (like Python 3 int objects, indeed, Python 3 int objects are just Python 2 long objects)
      – juanpa.arrivillaga
      6 hours ago










    • @juanpa.arrivillaga now it makes sense to me :)
      – roganjosh
      6 hours ago












    up vote
    16
    down vote










    up vote
    16
    down vote









    It is because bool is a subclass of int in both Python 2 and 3.



    >>> issubclass(bool, int)
    True


    But the int implementation has changed.



    In Python 2, int was the one that was 32 or 64 bits, depending on the system, as opposed to arbitrary-length long.



    In Python 3, int is arbitrary-length - the long of Python 2 was renamed to int and the original Python 2 int dropped altogether.




    In Python 2 you get the exactly same behaviour for long objects 1L and 0L:



    Python 2.7.15rc1 (default, Apr 15 2018, 21:51:34) 
    [GCC 7.3.0] on linux2
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import sys
    >>> sys.getsizeof(1L)
    28
    >>> sys.getsizeof(0L)
    24



    The long/Python 3 int is a variable-length object, just like a tuple - when it is allocated, enough memory is allocated to hold all the binary digits required to represent it. The length of the variable part is stored in the object head. 0 requires no binary digits (its variable length is 0), but even 1 spills over, and requires extra digits.



    I.e. 0 is represented as binary string of length 0:



    <>


    and 1 is represented as a 30-bit binary string:



    <000000000000000000000000000001>


    The default configuration in Python uses 30 bits in a uint32_t; so 2**30 - 1 still fits in 28 bytes on x86-64, and 2**30 will require 32;



    2**30 - 1 will be presented as



    <111111111111111111111111111111>


    i.e. all 30 value bits set to 1; 2**30 will need more, and it will have internal representation



    <000000000000000000000000000001000000000000000000000000000000>



    As for True using 28 bytes instead of 24 - you need not worry. True is a singleton and therefore only 4 bytes are lost in total in any Python program, not 4 for every usage of True.






    share|improve this answer














    It is because bool is a subclass of int in both Python 2 and 3.



    >>> issubclass(bool, int)
    True


    But the int implementation has changed.



    In Python 2, int was the one that was 32 or 64 bits, depending on the system, as opposed to arbitrary-length long.



    In Python 3, int is arbitrary-length - the long of Python 2 was renamed to int and the original Python 2 int dropped altogether.




    In Python 2 you get the exactly same behaviour for long objects 1L and 0L:



    Python 2.7.15rc1 (default, Apr 15 2018, 21:51:34) 
    [GCC 7.3.0] on linux2
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import sys
    >>> sys.getsizeof(1L)
    28
    >>> sys.getsizeof(0L)
    24



    The long/Python 3 int is a variable-length object, just like a tuple - when it is allocated, enough memory is allocated to hold all the binary digits required to represent it. The length of the variable part is stored in the object head. 0 requires no binary digits (its variable length is 0), but even 1 spills over, and requires extra digits.



    I.e. 0 is represented as binary string of length 0:



    <>


    and 1 is represented as a 30-bit binary string:



    <000000000000000000000000000001>


    The default configuration in Python uses 30 bits in a uint32_t; so 2**30 - 1 still fits in 28 bytes on x86-64, and 2**30 will require 32;



    2**30 - 1 will be presented as



    <111111111111111111111111111111>


    i.e. all 30 value bits set to 1; 2**30 will need more, and it will have internal representation



    <000000000000000000000000000001000000000000000000000000000000>



    As for True using 28 bytes instead of 24 - you need not worry. True is a singleton and therefore only 4 bytes are lost in total in any Python program, not 4 for every usage of True.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 6 hours ago

























    answered 7 hours ago









    Antti Haapala

    76.5k16143189




    76.5k16143189











    • Yep, and long objects just use no extra pointer to represent 0
      – juanpa.arrivillaga
      7 hours ago






    • 2




      @roganjosh they are the same type. That doesn't mean they have the same size. sys.getsizeof([1,2,3,4,5]) and sys.getsizeof() are not the same...
      – juanpa.arrivillaga
      7 hours ago










    • @roganjosh int objects in Python 2 were always the same size. long objects were arbitrarily-sized (like Python 3 int objects, indeed, Python 3 int objects are just Python 2 long objects)
      – juanpa.arrivillaga
      6 hours ago










    • @juanpa.arrivillaga now it makes sense to me :)
      – roganjosh
      6 hours ago
















    • Yep, and long objects just use no extra pointer to represent 0
      – juanpa.arrivillaga
      7 hours ago






    • 2




      @roganjosh they are the same type. That doesn't mean they have the same size. sys.getsizeof([1,2,3,4,5]) and sys.getsizeof() are not the same...
      – juanpa.arrivillaga
      7 hours ago










    • @roganjosh int objects in Python 2 were always the same size. long objects were arbitrarily-sized (like Python 3 int objects, indeed, Python 3 int objects are just Python 2 long objects)
      – juanpa.arrivillaga
      6 hours ago










    • @juanpa.arrivillaga now it makes sense to me :)
      – roganjosh
      6 hours ago















    Yep, and long objects just use no extra pointer to represent 0
    – juanpa.arrivillaga
    7 hours ago




    Yep, and long objects just use no extra pointer to represent 0
    – juanpa.arrivillaga
    7 hours ago




    2




    2




    @roganjosh they are the same type. That doesn't mean they have the same size. sys.getsizeof([1,2,3,4,5]) and sys.getsizeof() are not the same...
    – juanpa.arrivillaga
    7 hours ago




    @roganjosh they are the same type. That doesn't mean they have the same size. sys.getsizeof([1,2,3,4,5]) and sys.getsizeof() are not the same...
    – juanpa.arrivillaga
    7 hours ago












    @roganjosh int objects in Python 2 were always the same size. long objects were arbitrarily-sized (like Python 3 int objects, indeed, Python 3 int objects are just Python 2 long objects)
    – juanpa.arrivillaga
    6 hours ago




    @roganjosh int objects in Python 2 were always the same size. long objects were arbitrarily-sized (like Python 3 int objects, indeed, Python 3 int objects are just Python 2 long objects)
    – juanpa.arrivillaga
    6 hours ago












    @juanpa.arrivillaga now it makes sense to me :)
    – roganjosh
    6 hours ago




    @juanpa.arrivillaga now it makes sense to me :)
    – roganjosh
    6 hours ago












    up vote
    6
    down vote













    Both True and False are longobjects in CPython:




    struct _longobject _Py_FalseStruct = 
    PyVarObject_HEAD_INIT(&PyBool_Type, 0)
    0
    ;

    struct _longobject _Py_TrueStruct =
    PyVarObject_HEAD_INIT(&PyBool_Type, 1)
    1
    ;



    You thus can say that a Boolean is a subclass of a python-3.x int where True takes as value 1, and False takes as value 0. We thus make a call to PyVarObject_HEAD_INIT with as type parameter a reference to PyBool_Type and with ob_size as value 0 and 1 respectively.



    Now since python-3.x, there is no long anymore: these have been merged, and the int object will, depending on the size of the number, take a different value.



    If we inspect the source code of the longlobject type, we see:




    /* Long integer representation.
    The absolute value of a number is equal to
    SUM(for i=0 through abs(ob_size)-1) ob_digit[i] * 2**(SHIFT*i)
    Negative numbers are represented with ob_size < 0;
    zero is represented by ob_size == 0.
    In a normalized number, ob_digit[abs(ob_size)-1] (the most significant
    digit) is never zero. Also, in all cases, for all valid i,
    0 <= ob_digit[i] <= MASK.
    The allocation function takes care of allocating extra memory
    so that ob_digit[0] ... ob_digit[abs(ob_size)-1] are actually available.
    CAUTION: Generic code manipulating subtypes of PyVarObject has to
    aware that ints abuse ob_size's sign bit.
    */

    struct _longobject
    PyObject_VAR_HEAD
    digit ob_digit[1];
    ;



    To make a long story short, an _longobject can be seen as an array of "digits", but you should here see digits not as decimal digits, but as groups of bits that thus can be added, multiplied, etc.



    Now as is specified in the comment, it says that:




     zero is represented by ob_size == 0.



    So in case the value is zero, no digits are added, whereas for small integers (values less than 230 in CPython), it takes one digit, and so on.






    share|improve this answer


























      up vote
      6
      down vote













      Both True and False are longobjects in CPython:




      struct _longobject _Py_FalseStruct = 
      PyVarObject_HEAD_INIT(&PyBool_Type, 0)
      0
      ;

      struct _longobject _Py_TrueStruct =
      PyVarObject_HEAD_INIT(&PyBool_Type, 1)
      1
      ;



      You thus can say that a Boolean is a subclass of a python-3.x int where True takes as value 1, and False takes as value 0. We thus make a call to PyVarObject_HEAD_INIT with as type parameter a reference to PyBool_Type and with ob_size as value 0 and 1 respectively.



      Now since python-3.x, there is no long anymore: these have been merged, and the int object will, depending on the size of the number, take a different value.



      If we inspect the source code of the longlobject type, we see:




      /* Long integer representation.
      The absolute value of a number is equal to
      SUM(for i=0 through abs(ob_size)-1) ob_digit[i] * 2**(SHIFT*i)
      Negative numbers are represented with ob_size < 0;
      zero is represented by ob_size == 0.
      In a normalized number, ob_digit[abs(ob_size)-1] (the most significant
      digit) is never zero. Also, in all cases, for all valid i,
      0 <= ob_digit[i] <= MASK.
      The allocation function takes care of allocating extra memory
      so that ob_digit[0] ... ob_digit[abs(ob_size)-1] are actually available.
      CAUTION: Generic code manipulating subtypes of PyVarObject has to
      aware that ints abuse ob_size's sign bit.
      */

      struct _longobject
      PyObject_VAR_HEAD
      digit ob_digit[1];
      ;



      To make a long story short, an _longobject can be seen as an array of "digits", but you should here see digits not as decimal digits, but as groups of bits that thus can be added, multiplied, etc.



      Now as is specified in the comment, it says that:




       zero is represented by ob_size == 0.



      So in case the value is zero, no digits are added, whereas for small integers (values less than 230 in CPython), it takes one digit, and so on.






      share|improve this answer
























        up vote
        6
        down vote










        up vote
        6
        down vote









        Both True and False are longobjects in CPython:




        struct _longobject _Py_FalseStruct = 
        PyVarObject_HEAD_INIT(&PyBool_Type, 0)
        0
        ;

        struct _longobject _Py_TrueStruct =
        PyVarObject_HEAD_INIT(&PyBool_Type, 1)
        1
        ;



        You thus can say that a Boolean is a subclass of a python-3.x int where True takes as value 1, and False takes as value 0. We thus make a call to PyVarObject_HEAD_INIT with as type parameter a reference to PyBool_Type and with ob_size as value 0 and 1 respectively.



        Now since python-3.x, there is no long anymore: these have been merged, and the int object will, depending on the size of the number, take a different value.



        If we inspect the source code of the longlobject type, we see:




        /* Long integer representation.
        The absolute value of a number is equal to
        SUM(for i=0 through abs(ob_size)-1) ob_digit[i] * 2**(SHIFT*i)
        Negative numbers are represented with ob_size < 0;
        zero is represented by ob_size == 0.
        In a normalized number, ob_digit[abs(ob_size)-1] (the most significant
        digit) is never zero. Also, in all cases, for all valid i,
        0 <= ob_digit[i] <= MASK.
        The allocation function takes care of allocating extra memory
        so that ob_digit[0] ... ob_digit[abs(ob_size)-1] are actually available.
        CAUTION: Generic code manipulating subtypes of PyVarObject has to
        aware that ints abuse ob_size's sign bit.
        */

        struct _longobject
        PyObject_VAR_HEAD
        digit ob_digit[1];
        ;



        To make a long story short, an _longobject can be seen as an array of "digits", but you should here see digits not as decimal digits, but as groups of bits that thus can be added, multiplied, etc.



        Now as is specified in the comment, it says that:




         zero is represented by ob_size == 0.



        So in case the value is zero, no digits are added, whereas for small integers (values less than 230 in CPython), it takes one digit, and so on.






        share|improve this answer














        Both True and False are longobjects in CPython:




        struct _longobject _Py_FalseStruct = 
        PyVarObject_HEAD_INIT(&PyBool_Type, 0)
        0
        ;

        struct _longobject _Py_TrueStruct =
        PyVarObject_HEAD_INIT(&PyBool_Type, 1)
        1
        ;



        You thus can say that a Boolean is a subclass of a python-3.x int where True takes as value 1, and False takes as value 0. We thus make a call to PyVarObject_HEAD_INIT with as type parameter a reference to PyBool_Type and with ob_size as value 0 and 1 respectively.



        Now since python-3.x, there is no long anymore: these have been merged, and the int object will, depending on the size of the number, take a different value.



        If we inspect the source code of the longlobject type, we see:




        /* Long integer representation.
        The absolute value of a number is equal to
        SUM(for i=0 through abs(ob_size)-1) ob_digit[i] * 2**(SHIFT*i)
        Negative numbers are represented with ob_size < 0;
        zero is represented by ob_size == 0.
        In a normalized number, ob_digit[abs(ob_size)-1] (the most significant
        digit) is never zero. Also, in all cases, for all valid i,
        0 <= ob_digit[i] <= MASK.
        The allocation function takes care of allocating extra memory
        so that ob_digit[0] ... ob_digit[abs(ob_size)-1] are actually available.
        CAUTION: Generic code manipulating subtypes of PyVarObject has to
        aware that ints abuse ob_size's sign bit.
        */

        struct _longobject
        PyObject_VAR_HEAD
        digit ob_digit[1];
        ;



        To make a long story short, an _longobject can be seen as an array of "digits", but you should here see digits not as decimal digits, but as groups of bits that thus can be added, multiplied, etc.



        Now as is specified in the comment, it says that:




         zero is represented by ob_size == 0.



        So in case the value is zero, no digits are added, whereas for small integers (values less than 230 in CPython), it takes one digit, and so on.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 15 mins ago









        Peter Mortensen

        13.2k1983111




        13.2k1983111










        answered 7 hours ago









        Willem Van Onsem

        134k16126214




        134k16126214




















            up vote
            3
            down vote













            I haven't seen CPython code for this, but I believe this has something to do with optimization of integers in Python 3. Probably, as long was dropped, some optimizations were unified. int in Python 3 is arbitrary-sized int – the same as long was in Python 2. As bool stores in the same way as new int, it affects both.



            Interesting part:



            >>> (0).__sizeof__()
            24

            >>> (1).__sizeof__() # Here one more "block" is allocated
            28

            >>> (2**30-1).__sizeof__() # This is the maximum integer size fitting into 28
            28


            + bytes for object headers should complete the equation.






            share|improve this answer






















            • Actually, now in Python 3, int is just what Python 2 long was, it was really int that was "dropped"
              – juanpa.arrivillaga
              7 hours ago










            • Internally – absolutely true, I'm talking about names, but thx for clarification
              – Slam
              7 hours ago










            • Indeed, in CPython 3 source code, it's still longobject
              – juanpa.arrivillaga
              7 hours ago










            • It is actually deoptimization... pessimization?
              – Antti Haapala
              6 hours ago










            • It's probably not. I may be wrong, but this overhead does not cost as much as two different types + seamless cast in runtime. The truth is, you rarely operate such a huge amount of ints in normal python program to care about this extra memory. If you do – you should use something like numpy to run with ~0 overhead and have pure int32/64 – no headers, no reallocation. But overflows from time to time )
              – Slam
              6 hours ago














            up vote
            3
            down vote













            I haven't seen CPython code for this, but I believe this has something to do with optimization of integers in Python 3. Probably, as long was dropped, some optimizations were unified. int in Python 3 is arbitrary-sized int – the same as long was in Python 2. As bool stores in the same way as new int, it affects both.



            Interesting part:



            >>> (0).__sizeof__()
            24

            >>> (1).__sizeof__() # Here one more "block" is allocated
            28

            >>> (2**30-1).__sizeof__() # This is the maximum integer size fitting into 28
            28


            + bytes for object headers should complete the equation.






            share|improve this answer






















            • Actually, now in Python 3, int is just what Python 2 long was, it was really int that was "dropped"
              – juanpa.arrivillaga
              7 hours ago










            • Internally – absolutely true, I'm talking about names, but thx for clarification
              – Slam
              7 hours ago










            • Indeed, in CPython 3 source code, it's still longobject
              – juanpa.arrivillaga
              7 hours ago










            • It is actually deoptimization... pessimization?
              – Antti Haapala
              6 hours ago










            • It's probably not. I may be wrong, but this overhead does not cost as much as two different types + seamless cast in runtime. The truth is, you rarely operate such a huge amount of ints in normal python program to care about this extra memory. If you do – you should use something like numpy to run with ~0 overhead and have pure int32/64 – no headers, no reallocation. But overflows from time to time )
              – Slam
              6 hours ago












            up vote
            3
            down vote










            up vote
            3
            down vote









            I haven't seen CPython code for this, but I believe this has something to do with optimization of integers in Python 3. Probably, as long was dropped, some optimizations were unified. int in Python 3 is arbitrary-sized int – the same as long was in Python 2. As bool stores in the same way as new int, it affects both.



            Interesting part:



            >>> (0).__sizeof__()
            24

            >>> (1).__sizeof__() # Here one more "block" is allocated
            28

            >>> (2**30-1).__sizeof__() # This is the maximum integer size fitting into 28
            28


            + bytes for object headers should complete the equation.






            share|improve this answer














            I haven't seen CPython code for this, but I believe this has something to do with optimization of integers in Python 3. Probably, as long was dropped, some optimizations were unified. int in Python 3 is arbitrary-sized int – the same as long was in Python 2. As bool stores in the same way as new int, it affects both.



            Interesting part:



            >>> (0).__sizeof__()
            24

            >>> (1).__sizeof__() # Here one more "block" is allocated
            28

            >>> (2**30-1).__sizeof__() # This is the maximum integer size fitting into 28
            28


            + bytes for object headers should complete the equation.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited 23 mins ago









            Peter Mortensen

            13.2k1983111




            13.2k1983111










            answered 7 hours ago









            Slam

            3,34511832




            3,34511832











            • Actually, now in Python 3, int is just what Python 2 long was, it was really int that was "dropped"
              – juanpa.arrivillaga
              7 hours ago










            • Internally – absolutely true, I'm talking about names, but thx for clarification
              – Slam
              7 hours ago










            • Indeed, in CPython 3 source code, it's still longobject
              – juanpa.arrivillaga
              7 hours ago










            • It is actually deoptimization... pessimization?
              – Antti Haapala
              6 hours ago










            • It's probably not. I may be wrong, but this overhead does not cost as much as two different types + seamless cast in runtime. The truth is, you rarely operate such a huge amount of ints in normal python program to care about this extra memory. If you do – you should use something like numpy to run with ~0 overhead and have pure int32/64 – no headers, no reallocation. But overflows from time to time )
              – Slam
              6 hours ago
















            • Actually, now in Python 3, int is just what Python 2 long was, it was really int that was "dropped"
              – juanpa.arrivillaga
              7 hours ago










            • Internally – absolutely true, I'm talking about names, but thx for clarification
              – Slam
              7 hours ago










            • Indeed, in CPython 3 source code, it's still longobject
              – juanpa.arrivillaga
              7 hours ago










            • It is actually deoptimization... pessimization?
              – Antti Haapala
              6 hours ago










            • It's probably not. I may be wrong, but this overhead does not cost as much as two different types + seamless cast in runtime. The truth is, you rarely operate such a huge amount of ints in normal python program to care about this extra memory. If you do – you should use something like numpy to run with ~0 overhead and have pure int32/64 – no headers, no reallocation. But overflows from time to time )
              – Slam
              6 hours ago















            Actually, now in Python 3, int is just what Python 2 long was, it was really int that was "dropped"
            – juanpa.arrivillaga
            7 hours ago




            Actually, now in Python 3, int is just what Python 2 long was, it was really int that was "dropped"
            – juanpa.arrivillaga
            7 hours ago












            Internally – absolutely true, I'm talking about names, but thx for clarification
            – Slam
            7 hours ago




            Internally – absolutely true, I'm talking about names, but thx for clarification
            – Slam
            7 hours ago












            Indeed, in CPython 3 source code, it's still longobject
            – juanpa.arrivillaga
            7 hours ago




            Indeed, in CPython 3 source code, it's still longobject
            – juanpa.arrivillaga
            7 hours ago












            It is actually deoptimization... pessimization?
            – Antti Haapala
            6 hours ago




            It is actually deoptimization... pessimization?
            – Antti Haapala
            6 hours ago












            It's probably not. I may be wrong, but this overhead does not cost as much as two different types + seamless cast in runtime. The truth is, you rarely operate such a huge amount of ints in normal python program to care about this extra memory. If you do – you should use something like numpy to run with ~0 overhead and have pure int32/64 – no headers, no reallocation. But overflows from time to time )
            – Slam
            6 hours ago




            It's probably not. I may be wrong, but this overhead does not cost as much as two different types + seamless cast in runtime. The truth is, you rarely operate such a huge amount of ints in normal python program to care about this extra memory. If you do – you should use something like numpy to run with ~0 overhead and have pure int32/64 – no headers, no reallocation. But overflows from time to time )
            – Slam
            6 hours ago










            up vote
            2
            down vote













            Take a look at the cpython code for True and False



            Internally it is represented as integer



            PyTypeObject PyBool_Type = 
            PyVarObject_HEAD_INIT(&PyType_Type, 0)
            "bool",
            sizeof(struct _longobject),
            0,
            0, /* tp_dealloc */
            0, /* tp_print */
            0, /* tp_getattr */
            0, /* tp_setattr */
            0, /* tp_reserved */
            bool_repr, /* tp_repr */
            &bool_as_number, /* tp_as_number */
            0, /* tp_as_sequence */
            0, /* tp_as_mapping */
            0, /* tp_hash */
            0, /* tp_call */
            bool_repr, /* tp_str */
            0, /* tp_getattro */
            0, /* tp_setattro */
            0, /* tp_as_buffer */
            Py_TPFLAGS_DEFAULT, /* tp_flags */
            bool_doc, /* tp_doc */
            0, /* tp_traverse */
            0, /* tp_clear */
            0, /* tp_richcompare */
            0, /* tp_weaklistoffset */
            0, /* tp_iter */
            0, /* tp_iternext */
            0, /* tp_methods */
            0, /* tp_members */
            0, /* tp_getset */
            &PyLong_Type, /* tp_base */
            0, /* tp_dict */
            0, /* tp_descr_get */
            0, /* tp_descr_set */
            0, /* tp_dictoffset */
            0, /* tp_init */
            0, /* tp_alloc */
            bool_new, /* tp_new */
            ;

            /* The objects representing bool values False and True */

            struct _longobject _Py_FalseStruct =
            PyVarObject_HEAD_INIT(&PyBool_Type, 0)
            0
            ;

            struct _longobject _Py_TrueStruct = {
            PyVarObject_HEAD_INIT(&PyBool_Type, 1)
            1





            share|improve this answer






















            • I don't know why this was downvoted
              – Antti Haapala
              6 hours ago










            • I think i just was not as quick to answer properly as others :)
              – Kamil Niski
              6 hours ago










            • The answer only gets halfway there. It's represented as an integer.. yeah? And so what?
              – wim
              6 hours ago










            • @wim I don't see the need to explain it further since guys above already did great job at this. I don't want to duplicate content. Please refer to their answers.
              – Kamil Niski
              6 hours ago







            • 2




              I think so, but it's up to you. Should you wait for it to maybe get +3 and then delete you may earn a disciplined badge... :)
              – wim
              5 hours ago















            up vote
            2
            down vote













            Take a look at the cpython code for True and False



            Internally it is represented as integer



            PyTypeObject PyBool_Type = 
            PyVarObject_HEAD_INIT(&PyType_Type, 0)
            "bool",
            sizeof(struct _longobject),
            0,
            0, /* tp_dealloc */
            0, /* tp_print */
            0, /* tp_getattr */
            0, /* tp_setattr */
            0, /* tp_reserved */
            bool_repr, /* tp_repr */
            &bool_as_number, /* tp_as_number */
            0, /* tp_as_sequence */
            0, /* tp_as_mapping */
            0, /* tp_hash */
            0, /* tp_call */
            bool_repr, /* tp_str */
            0, /* tp_getattro */
            0, /* tp_setattro */
            0, /* tp_as_buffer */
            Py_TPFLAGS_DEFAULT, /* tp_flags */
            bool_doc, /* tp_doc */
            0, /* tp_traverse */
            0, /* tp_clear */
            0, /* tp_richcompare */
            0, /* tp_weaklistoffset */
            0, /* tp_iter */
            0, /* tp_iternext */
            0, /* tp_methods */
            0, /* tp_members */
            0, /* tp_getset */
            &PyLong_Type, /* tp_base */
            0, /* tp_dict */
            0, /* tp_descr_get */
            0, /* tp_descr_set */
            0, /* tp_dictoffset */
            0, /* tp_init */
            0, /* tp_alloc */
            bool_new, /* tp_new */
            ;

            /* The objects representing bool values False and True */

            struct _longobject _Py_FalseStruct =
            PyVarObject_HEAD_INIT(&PyBool_Type, 0)
            0
            ;

            struct _longobject _Py_TrueStruct = {
            PyVarObject_HEAD_INIT(&PyBool_Type, 1)
            1





            share|improve this answer






















            • I don't know why this was downvoted
              – Antti Haapala
              6 hours ago










            • I think i just was not as quick to answer properly as others :)
              – Kamil Niski
              6 hours ago










            • The answer only gets halfway there. It's represented as an integer.. yeah? And so what?
              – wim
              6 hours ago










            • @wim I don't see the need to explain it further since guys above already did great job at this. I don't want to duplicate content. Please refer to their answers.
              – Kamil Niski
              6 hours ago







            • 2




              I think so, but it's up to you. Should you wait for it to maybe get +3 and then delete you may earn a disciplined badge... :)
              – wim
              5 hours ago













            up vote
            2
            down vote










            up vote
            2
            down vote









            Take a look at the cpython code for True and False



            Internally it is represented as integer



            PyTypeObject PyBool_Type = 
            PyVarObject_HEAD_INIT(&PyType_Type, 0)
            "bool",
            sizeof(struct _longobject),
            0,
            0, /* tp_dealloc */
            0, /* tp_print */
            0, /* tp_getattr */
            0, /* tp_setattr */
            0, /* tp_reserved */
            bool_repr, /* tp_repr */
            &bool_as_number, /* tp_as_number */
            0, /* tp_as_sequence */
            0, /* tp_as_mapping */
            0, /* tp_hash */
            0, /* tp_call */
            bool_repr, /* tp_str */
            0, /* tp_getattro */
            0, /* tp_setattro */
            0, /* tp_as_buffer */
            Py_TPFLAGS_DEFAULT, /* tp_flags */
            bool_doc, /* tp_doc */
            0, /* tp_traverse */
            0, /* tp_clear */
            0, /* tp_richcompare */
            0, /* tp_weaklistoffset */
            0, /* tp_iter */
            0, /* tp_iternext */
            0, /* tp_methods */
            0, /* tp_members */
            0, /* tp_getset */
            &PyLong_Type, /* tp_base */
            0, /* tp_dict */
            0, /* tp_descr_get */
            0, /* tp_descr_set */
            0, /* tp_dictoffset */
            0, /* tp_init */
            0, /* tp_alloc */
            bool_new, /* tp_new */
            ;

            /* The objects representing bool values False and True */

            struct _longobject _Py_FalseStruct =
            PyVarObject_HEAD_INIT(&PyBool_Type, 0)
            0
            ;

            struct _longobject _Py_TrueStruct = {
            PyVarObject_HEAD_INIT(&PyBool_Type, 1)
            1





            share|improve this answer














            Take a look at the cpython code for True and False



            Internally it is represented as integer



            PyTypeObject PyBool_Type = 
            PyVarObject_HEAD_INIT(&PyType_Type, 0)
            "bool",
            sizeof(struct _longobject),
            0,
            0, /* tp_dealloc */
            0, /* tp_print */
            0, /* tp_getattr */
            0, /* tp_setattr */
            0, /* tp_reserved */
            bool_repr, /* tp_repr */
            &bool_as_number, /* tp_as_number */
            0, /* tp_as_sequence */
            0, /* tp_as_mapping */
            0, /* tp_hash */
            0, /* tp_call */
            bool_repr, /* tp_str */
            0, /* tp_getattro */
            0, /* tp_setattro */
            0, /* tp_as_buffer */
            Py_TPFLAGS_DEFAULT, /* tp_flags */
            bool_doc, /* tp_doc */
            0, /* tp_traverse */
            0, /* tp_clear */
            0, /* tp_richcompare */
            0, /* tp_weaklistoffset */
            0, /* tp_iter */
            0, /* tp_iternext */
            0, /* tp_methods */
            0, /* tp_members */
            0, /* tp_getset */
            &PyLong_Type, /* tp_base */
            0, /* tp_dict */
            0, /* tp_descr_get */
            0, /* tp_descr_set */
            0, /* tp_dictoffset */
            0, /* tp_init */
            0, /* tp_alloc */
            bool_new, /* tp_new */
            ;

            /* The objects representing bool values False and True */

            struct _longobject _Py_FalseStruct =
            PyVarObject_HEAD_INIT(&PyBool_Type, 0)
            0
            ;

            struct _longobject _Py_TrueStruct = {
            PyVarObject_HEAD_INIT(&PyBool_Type, 1)
            1






            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited 6 hours ago

























            answered 7 hours ago









            Kamil Niski

            1,950111




            1,950111











            • I don't know why this was downvoted
              – Antti Haapala
              6 hours ago










            • I think i just was not as quick to answer properly as others :)
              – Kamil Niski
              6 hours ago










            • The answer only gets halfway there. It's represented as an integer.. yeah? And so what?
              – wim
              6 hours ago










            • @wim I don't see the need to explain it further since guys above already did great job at this. I don't want to duplicate content. Please refer to their answers.
              – Kamil Niski
              6 hours ago







            • 2




              I think so, but it's up to you. Should you wait for it to maybe get +3 and then delete you may earn a disciplined badge... :)
              – wim
              5 hours ago

















            • I don't know why this was downvoted
              – Antti Haapala
              6 hours ago










            • I think i just was not as quick to answer properly as others :)
              – Kamil Niski
              6 hours ago










            • The answer only gets halfway there. It's represented as an integer.. yeah? And so what?
              – wim
              6 hours ago










            • @wim I don't see the need to explain it further since guys above already did great job at this. I don't want to duplicate content. Please refer to their answers.
              – Kamil Niski
              6 hours ago







            • 2




              I think so, but it's up to you. Should you wait for it to maybe get +3 and then delete you may earn a disciplined badge... :)
              – wim
              5 hours ago
















            I don't know why this was downvoted
            – Antti Haapala
            6 hours ago




            I don't know why this was downvoted
            – Antti Haapala
            6 hours ago












            I think i just was not as quick to answer properly as others :)
            – Kamil Niski
            6 hours ago




            I think i just was not as quick to answer properly as others :)
            – Kamil Niski
            6 hours ago












            The answer only gets halfway there. It's represented as an integer.. yeah? And so what?
            – wim
            6 hours ago




            The answer only gets halfway there. It's represented as an integer.. yeah? And so what?
            – wim
            6 hours ago












            @wim I don't see the need to explain it further since guys above already did great job at this. I don't want to duplicate content. Please refer to their answers.
            – Kamil Niski
            6 hours ago





            @wim I don't see the need to explain it further since guys above already did great job at this. I don't want to duplicate content. Please refer to their answers.
            – Kamil Niski
            6 hours ago





            2




            2




            I think so, but it's up to you. Should you wait for it to maybe get +3 and then delete you may earn a disciplined badge... :)
            – wim
            5 hours ago





            I think so, but it's up to you. Should you wait for it to maybe get +3 and then delete you may earn a disciplined badge... :)
            – wim
            5 hours ago


















             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53015922%2fdifferent-object-size-of-true-and-false-in-python-3%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?