This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mark.dickinson
Recipients ajaksu2, amaury.forgeotdarc, georg.brandl, mark.dickinson, pitrou
Date 2009-02-13.11:57:52
SpamBayes Score 1.978806e-11
Marked as misclassified No
Message-id <>
> BTW, there's a warning in _struct.c:180 -> warning: ‘get_ulong’
> defined but not used, should I open a new issue?

Sure.  Please could you add me to the nosy list if you do.

In my opinion, the struct module *really* needs an overhaul, especially
for py3k; there's a lot of inconsistency in the behaviour with respect
to different integer types, and there's a lot of code that seems to be
there purely for backwards compatibility that could be removed for 3.1
(and probably for 2.7 as well):  for example, allowing floats when
packing integer types, and allowing overflow to wraparound rather than
raising an exception.

Would it be worth opening a general 'overhaul the struct module' issue
and marking all the current struct bugs as dependencies for this issue?
Date User Action Args
2009-02-13 11:58:34mark.dickinsonsetrecipients: + mark.dickinson, georg.brandl, amaury.forgeotdarc, pitrou, ajaksu2
2009-02-13 11:58:16mark.dickinsonsetmessageid: <>
2009-02-13 11:58:08mark.dickinsonlinkissue3694 messages
2009-02-13 11:57:57mark.dickinsoncreate