PEP 451: Resolve dangling hyphens (#3352)
This commit is contained in:
parent
938f17e4cd
commit
7dd8829bcf
10
pep-0451.txt
10
pep-0451.txt
|
@ -678,9 +678,9 @@ Other than adding ``__spec__``, none of the import-related module
|
|||
attributes will be changed or deprecated, though some of them could be;
|
||||
any such deprecation can wait until Python 4.
|
||||
|
||||
A module's spec will not be kept in sync with the corresponding import-
|
||||
related attributes. Though they may differ, in practice they will
|
||||
typically be the same.
|
||||
A module's spec will not be kept in sync with the corresponding
|
||||
import-related attributes. Though they may differ, in practice they
|
||||
will typically be the same.
|
||||
|
||||
One notable exception is that case where a module is run as a script by
|
||||
using the ``-m`` flag. In that case ``module.__spec__.name`` will
|
||||
|
@ -716,8 +716,8 @@ Adding yet another similar method to loaders is a case of practicality.
|
|||
find_module() could be changed to return specs instead of loaders.
|
||||
This is tempting because the import APIs have suffered enough,
|
||||
especially considering PathEntryFinder.find_loader() was just
|
||||
added in Python 3.3. However, the extra complexity and a less-than-
|
||||
explicit method name aren't worth it.
|
||||
added in Python 3.3. However, the extra complexity and a
|
||||
less-than-explicit method name aren't worth it.
|
||||
|
||||
The "target" parameter of find_spec()
|
||||
-------------------------------------
|
||||
|
|
Loading…
Reference in New Issue