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, mark.dickinson, theller, vdupras
Date 2009-07-04.21:48:10
SpamBayes Score 2.019294e-08
Marked as misclassified No
Message-id <>
Here's a patch that does some general cleanup of the object->integer 
helper functions in the struct module;  in the process, it fixes this 
bug.  With this patch, all conversions from a PyObject to a C integer go 
through get_pylong, so they're all treated the same way.  Currently 
(i.e., without the patch) there's a lack of consistency in the way the 
various integer codes are handled---some codes emit a warning for float 
conversions and some ('q', 'Q') don't;  some codes will happily convert 
a Decimal instance, and others won't.  Some codes produce this strange 
'unsupported operand types' message and some don't, etc.
Date User Action Args
2009-07-04 21:48:13mark.dickinsonsetrecipients: + mark.dickinson, theller, ajaksu2, vdupras
2009-07-04 21:48:13mark.dickinsonsetmessageid: <>
2009-07-04 21:48:12mark.dickinsonlinkissue1741130 messages
2009-07-04 21:48:12mark.dickinsoncreate