Thomas Wouters wrote: > If 2.5 warns and does the old thing, the upgrade path is easy and > defendable. This is also why there are future statements -- I > distinctly recall making the same argument back then :-) The cost of > continuing the misfeatures in struct for one release does not weigh > up to the cost of breaking compatibility unwarned. This really sounds to me like a __future__ import would be useful to get the fixed behaviour. Tim Delaney
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