Fix PEP 488 to follow the proper meaning of the debug_override

argument for importlib.util.cache_from_source() (PEP originally had
the semantics reversed for True/False values).

The change does not change the outcome of the backwards-compatibility
section and thus is considered a minor change.
This commit is contained in:
Brett Cannon 2015-03-27 14:40:51 -04:00
parent 083f942a52
commit 8958f2df0d
1 changed files with 4 additions and 4 deletions

View File

@ -180,10 +180,10 @@ While this might lead to long file names, it is assumed that most
users never look at the contents of the __pycache__ directory and so users never look at the contents of the __pycache__ directory and so
this won't be an issue. this won't be an issue.
The ``debug_override`` parameter will be deprecated. As the parameter The ``debug_override`` parameter will be deprecated. A ``False``
expects a boolean, the integer value of the boolean will be used as value will be equivalent to ``optimization=1`` while a ``True``
if it had been provided as the argument to ``optimization`` (a value will represent ``optimization=''`` (a ``None`` argument will
``None`` argument will mean the same as for ``optimization``). A continue to mean the same as for ``optimization``). A
deprecation warning will be raised when ``debug_override`` is given a deprecation warning will be raised when ``debug_override`` is given a
value other than ``None``, but there are no plans for the complete value other than ``None``, but there are no plans for the complete
removal of the parameter at this time (but removal will be no later removal of the parameter at this time (but removal will be no later