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).
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com