"M.-A. Lemburg" <mal@lemburg.com> writes: > 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. In case this isn't clear yet: There likely will be no compatibility problems. The bit manipulations will likely see the same results. Of course, it would be good if users bring forward examples of how the change affects their code. I.e. whenever you see such a warning, please study the code and report whether the upcoming change will or will not break your code. Such reports would allow to improve the documentation. Regards, Martin
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