-
Notifications
You must be signed in to change notification settings - Fork 52
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
library
envs share a namespace with filesystem
envs and cannot have the same name
#72
Comments
This error
can be fixed by adding this kwarg to def conda_pack(prefix, output):
import conda_pack
conda_pack.pack(prefix=str(prefix), output=str(output), ignore_missing_files=True)
# ^^^^^^^^^^^^^^^^^^^^^^^^^ ... but I don't think we want to do that. |
It then enters into a never ending loop of failed attempts to build the environment, one attempt per copy each, like a table tennis game... :) |
Chris and I talked about this. One of the issues discussed here is that This is is just a small issue. The missing files issue is a different one and has nothing to do with this. I'll open more issues to address them individually. |
library
env triggers a filesystem
env copy envs share a namespace with
filesystem` envs and cannot have the same name
envs share a namespace with
filesystem` envs and cannot have the same namelibrary
envs share a namespace with filesystem
envs and cannot have the same name
This must be an error with conda-store not properly checking that the |
This is now fixed with #96 |
With a fresh local deployment (no previous env created), creating an empty env with just
python
results in a second copy.Env:
Relevant log lines:
I am guessing the other errors I have seen might be due to mutual overwrites between the copies.
Any idea why this is happening and how can I prevent this?
The text was updated successfully, but these errors were encountered: