-
Notifications
You must be signed in to change notification settings - Fork 9
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
write permission mishaps #330
Comments
conda list example:
|
Was the environment not write protected before? I don't recall getting errors like this in the past |
I think this has been happening for a while, but not since the first env. It's been write-protected since the start but this cropped up somewhere in 5.7.something iirc |
Adding a new case to the description: an environment that has been write-protected and then conda-pack -ed cannot be unpacked properly. I ran into this today because for the first time in a while I had created environments in my home area via the "apply release" script (to test the script) rather than from the yaml file or as the originating template for the environment release. |
The |
conda list
give annoying warnings.__pycache__
folders, do these get created properly in a write-protected env?The text was updated successfully, but these errors were encountered: