Message81911
Unsupported provider
> 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:34 | mark.dickinson | set | recipients:
+ mark.dickinson, georg.brandl, amaury.forgeotdarc, pitrou, ajaksu2 |
2009-02-13 11:58:16 | mark.dickinson | set | messageid: <1234526296.3.0.0277646558882.issue3694@psf.upfronthosting.co.za> |
2009-02-13 11:58:08 | mark.dickinson | link | issue3694 messages |
2009-02-13 11:57:57 | mark.dickinson | create | |
|