[docs] [issue26821] array module "minimum size in bytes" table is wrong for int/long
Jonathan Booth
report at bugs.python.org
Thu Apr 21 18:25:03 EDT 2016
Jonathan Booth added the comment:
Ugly -- if I know I'm dealing with 4-byte data, I can't just specify 'I' or 'L' because it'll be wrong on some platform? Maybe the bug is really the module's design. Seems I need to look elsewhere for other reasons (array seems to want to copy memory, rather than sharing it, so I can't get two arrays one int, one byte with the same backing memory where changes to one effect the other), but that's all the more argument for me to switch off array anyway.
In any case, take it as the documentation wasn't particularly clear.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26821>
_______________________________________
More information about the docs
mailing list