Closed remram44 closed 2 years ago
Bump. Please look into this, still happening, super annoying.
The python community has abandoned namespace packages. Because getting them to work is super annoying.
Honestly, the user experience here has always been broken. And it's not conda's place--being a language-agnostic package manager--to fix it for the PyPA. (Nor do we even have the authority to.)
Rant over. You have a point. Conda can do better. And this issue should stay open as a bug until we can address it further.
Well, at least installing such packages work with other tools (e.g. pip).
Here's my workaround (commit): remove build dependencies in the conda recipe (since conda will break if installing them) and pass --single-version-externally-managed
to setup.py
@remram44 adding preserve_egg_dir: yes
to your recipe should do the trick. On Python 3 you can now use native PEP420 namespace packages (once #1090 is released).
Hi there, thank you for your contribution!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.
If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment.
Thanks!
I have two libs that share a namespace package, and one of them depends on the other.
When building the one that has the dependency, the build fails with "
OSError: File exists: <path to the namespace directory>
". It looks like you are not handling the fact that the directory will already have been created while installing the first package.