12.11.17 11:24, Nick Coghlan пише: > The PEP also proposes repurposing the existing FutureWarning category > to explicitly mean "backwards compatibility warnings that should be > shown to users of Python applications" since: > > - we don't tend to use FutureWarning for its original nominal purpose > (changes that will continue to run but will do something different) FutureWarning currently is used for its original nominal purpose in the re and ElementTree modules. It even had been added in 2.7 for behavior that already have been changed in Python 3 or will be changed in future versions (emitted only with the -3 option).
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