I have a namespace package called foo, which contains multiple distribution packages: foo.bar_one, foo.bar_two, and foo.bar_three are installed as distribution packages via pip from a private GitLab repository. These packages are installed under Python's site-packages, which is included in the PYTHONPATH. Additionally, in the project root, there is another directory also named foo, containing additional packages (e.g., foo.bar_z). The project root is also added to PYTHONPATH, allowing imports like import foo.bar_z as if all packages were in the same namespace. There are dependencies between some of these packages. foo.bar_z will also be published as a distribution package so that other projects can install it via pip, in which case it would reside in site-packages. The Issue: This setup works as expected on Windows with python 3.x (I can import both foo.bar_one and foo.bar_z), but on Linux, I encounter namespace-related import issues: If site-packages appears first in PYTHONPATH, I can import foo.bar_one, but foo.bar_z fails, stating that bar_z does not exist within the foo namespace. If the project root appears first in PYTHONPATH, I can import foo.bar_z, but foo.bar_one fails, stating that bar_one does not exist within the foo namespace. Questions: Is there a fundamental difference in how namespace packages are handled between Windows and Linux that causes this behavior? Is there a minor configuration change that can resolve this issue on Linux? If this setup is inherently flawed, what would be a better approach to achieve the same goal while maintaining compatibility? Any insights or recommendations on resolving this would be greatly appreciated! EDIT: Linux system has PYTHON_VERSION=3.12.7 Windows system has Python Version: 3.12.6 Continue reading...
