-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build fails if using namespace packages #649
Comments
Bump. Please look into this, still happening, super annoying. |
This reverts commit 4e601f9. This works around conda/conda-build#649.
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 |
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.The text was updated successfully, but these errors were encountered: