[Neil Schemenauer] > Shouldn't the entry in the __future__ file be: > > nested_scopes = _Feature((2, 1, 0, "beta", 1), (2, 2, 0, "alpha", 0)) > > or am I misunderstanding something? Until nested_scopes *is* the rule, the Mandatory Release field is just a guess about the future. Changing it to (2, 2, 0, "alpha", 0) right *now* would be wrong, since it would change it from a guess about the future to a false statement about the present. It must be changed when nested_scopes become mandatory; it needn't be changed before then (unless we delay making them mandatory beyond 2.2 final), although if somebody thinks they have a good use for moving the guess up, fine, just so long as they don't move the guess to or before 2.2a0.
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