PEP 395
E1280975
UNEXPLORED
PEP 395 is a Python Enhancement Proposal that defines guidelines and mechanisms for handling the `__name__` and `__main__` attributes to improve module naming, execution, and packaging consistency.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PEP 395 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T17557264 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PEP 395 Context triple: [PEP 420, relatedTo, PEP 395]
-
A.
PEP 345
PEP 345 is a Python Enhancement Proposal that defines the metadata format for Python software packages, including standardized fields used in package distribution.
-
B.
PEP 328
PEP 328 is a Python Enhancement Proposal that introduced and standardized the syntax and semantics for absolute and relative imports in Python.
-
C.
PEP 425
PEP 425 is a Python Enhancement Proposal that defines the standardized “compatibility tag” scheme used to identify which Python interpreter and platform a binary distribution (like a wheel) is compatible with.
-
D.
PEP 302
PEP 302 is a Python Enhancement Proposal that defines the import hook mechanism, enabling customization and extension of Python’s module import system.
-
E.
PEP 382
PEP 382 is a Python Enhancement Proposal that originally specified a mechanism for namespace packages using explicit “.pkg” files, an approach later superseded by the implicit namespace package model of PEP 420.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: PEP 395 Target entity description: PEP 395 is a Python Enhancement Proposal that defines guidelines and mechanisms for handling the `__name__` and `__main__` attributes to improve module naming, execution, and packaging consistency.
-
A.
PEP 345
PEP 345 is a Python Enhancement Proposal that defines the metadata format for Python software packages, including standardized fields used in package distribution.
-
B.
PEP 328
PEP 328 is a Python Enhancement Proposal that introduced and standardized the syntax and semantics for absolute and relative imports in Python.
-
C.
PEP 425
PEP 425 is a Python Enhancement Proposal that defines the standardized “compatibility tag” scheme used to identify which Python interpreter and platform a binary distribution (like a wheel) is compatible with.
-
D.
PEP 302
PEP 302 is a Python Enhancement Proposal that defines the import hook mechanism, enabling customization and extension of Python’s module import system.
-
E.
PEP 382
PEP 382 is a Python Enhancement Proposal that originally specified a mechanism for namespace packages using explicit “.pkg” files, an approach later superseded by the implicit namespace package model of PEP 420.
- F. None of above. chosen
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject linked to:
PEP 420 (namespace packages)