[Guido] > ... > - Stage 2 of the int/long integration (PEP 237). This mostly means > warning about situations where hex, oct or shift of an int returns a > different value than for the same value as a long. (I think the PEP > misses this step, but it's necessary -- we can't just change the > semantics silently without warning first.) It's unclear there whether you intend that a warning in 2.3 be coupled with (a) delivering the 2.2 result, or (b) delivering the new (auto-overflow) result. If a _future statement is introduced for this (incompatible changes are what __future__ is there for -- alas), #a is the obvious answer. > ... > Anything else? Nuking SET_LINENO remains the conceptually clearest way to get a >5% boost in pystone. As other high-frequency paths in the interpreter have gotten leaner, the speed benefit of -O has gotten larger.
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