You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The discover_package_path function fails to handle PEP 420 implicit namespaces, as it relies on finding init.py files to determine valid package paths. This causes issues when working with implicit namespaces, where such files are not required.
Desired Solution:
Separate the logic for explicit and implicit namespaces:
Explicit namespaces: Identify using __init__.py.
Implicit namespaces: Identify according to PEP 420.
Error handling: Raise an exception if neither condition is met.
Additional Context:
This issue comes from discussions in #10026 and relates to challenges observed in #10077, where missing or empty init.py files impacted pyreverse's to correctly identify detect package relationships.
The text was updated successfully, but these errors were encountered:
Current Problem:
The discover_package_path function fails to handle PEP 420 implicit namespaces, as it relies on finding init.py files to determine valid package paths. This causes issues when working with implicit namespaces, where such files are not required.
Desired Solution:
Separate the logic for explicit and implicit namespaces:
__init__.py
.Additional Context:
This issue comes from discussions in #10026 and relates to challenges observed in #10077, where missing or empty init.py files impacted pyreverse's to correctly identify detect package relationships.
The text was updated successfully, but these errors were encountered: