On Mon, Aug 12, 2002 at 12:19:06AM +0200, M.-A. Lemburg wrote: > Changing these semantics would cause compatibility problems for > applications doing low-level bit manipulations or ones which use > the Python integer type to store unsigned integer values, e.g. > for use as bitmapped flags. I'm very much in favor of this change but a deprecation warning is not enough - some suitable replacement should be provided to cryptographers and other bit fiddlers. Proposal: A standard module implementing the types [u]int[8|16|32|64]. These types would behave just like C integers - wrap around on overflow, etc and have a guaranteed size regardless of platform. They can even have methods for bit rotation. Oren
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