Bob Ippolito wrote:
> On May 29, 2006, at 8:00 PM, Tim Peters wrote:
>> We certainly don't want to see two deprecation warnings for a single
>> deprecated behavior. I suggest eliminating the "struct integer
>> wrapping" warning, mostly because I had no idea what it _meant_
>> before reading the comments in _struct.c ("wrapping" is used most
>> often in a proxy or delegation context in Python these days). "'B'
>> format requires 0 <= number <= 255" is perfectly clear all by itself.
>
> What should it be called instead of wrapping? When it says it's
> wrapping, it means that it's doing x &= (2 ^ (8 * n)) - 1 to force a
> number into meeting the expected range.
"integer overflow masking" perhaps?
> Reducing it to one warning instead of two is kinda difficult. Is it
> worth the trouble?
If there are cases where only one warning or the other triggers, it doesn't
seem worth the effort to try and suppress one of them when they both trigger.
Cheers,
Nick.
--
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
---------------------------------------------------------------
http://www.boredomandlaziness.org
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4