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 sgatwasetde
Recipients
Date 2004-11-11.22:20:46
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=1131807

Issuing a warning instead of an error might be a good idea 
(to give the user-base some time adapt).  
But then we still have to deal with the fact that the some 
python modules are broken on 64 bit (at least big-endian). 
The gzip module for example does not work correctly even 
with the old code (because of stuctmodule).  
And there is user code out there that relies on correct  
overflow detection (which was the reason i submitted the 
patch). 
 
Another way would be to omit the overflow detection 
completely and heave the user take care of it. This will break 
a lot of applications but is imho more consistent then the old   
behavior (check some cases on some architectures). 
 
Personally i would like to have a structmodule in python 2.4 
that works a one would expect (overflow detection) but that  
is not my decision to make. The fact that code which is 
under control of the python project uses struct.pack (...) in 
erroneous ways should be fixed (even if it does work on 32 
bit archs atm). 
History
Date User Action Args
2007-08-23 15:40:01adminlinkissue1038854 messages
2007-08-23 15:40:01admincreate