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
global packages are used instead of local, despite an environment being active. #7230
Comments
What is the output of |
|
If you want to try the latest prerelease conda version, use
|
Thank you, I will be switching to that. I've deleted and recreated envs 3 more times in the last week just because this issue kept popping up. |
Hmmmm, I have another problem that just started appearing after I upgraded to conda 4.6.0a2.
|
Yeah if you can come up with a sequence of commands that reproduce the error, so that I can reproduce it myself, I’ll try to figure out what’s going on. |
Actually, I can't do that, exactly. I suddenly couldn't activate any envs, so I've decided a fresh install is in order. |
The error you uploaded the report for was #7256. |
Ok, I did a fresh install, moved my old envs back,
|
After you update to conda 4.6.0a2, close your Anaconda Prompt shell, and then reopen it again. Does |
Still having pip problems, so I guess I'll do that fresh install. |
I’m guessing you’re choosing the “system install” / “install for all users” vs just the “for me only” install, right? If you’ve been doing the first, and you run into problems again, try a fresh install but this time do the “for me only” type. (I don’t remember off the top of my head what the exact names are for the options.) |
Really appreciate your patience and willingness to go back-and-forth here too. You’re actually the first person I’m interacting with who is using a 4.6 alpha on Windows. I do think it’s for the most part pretty solid. But especially on Windows there could be a few hiccups for conditions outside of what I’ve tested so far. |
I'm not sure what the option I selected when installing it for the first time, it probably was installed for all users. The other times I installed it today I selected to only install it for the current user. And it's nothing, you and your team create this wonderful tool I use pretty much every day, and I like to think I'm contributing somewhat by trying to help with finding bugs 😄 I actually do want to contribute more, but I don't think I'm good enough at anything to help with actual development. Ok, this time, I did some things different. This seems to have fixed the pip problem 😄 The problem of the shell command configuration is still there
Should I try running |
The AssertionError is still there when doing |
Hi there, thank you for your contribution to Conda! This issue has been automatically locked since it has not had recent activity after it was closed. Please open a new issue if needed. |
I'm submitting a...
Current Behavior
When running python scripts with an environment activated, it still uses packages from
<anaconda install path>\Lib\site-packages\
instead of<anaconda install path>\envs\<env>\Lib\site-packages\
I created a new environment after reading ContinuumIO/anaconda-issues#1429 (comment) , something I came across when trying to solve this, making sure that pip was installed when the environment was created, and it worked fine for a while. Then, it suddenly began to behave like this instead of what I expected. Also, de- and reactivating my env did not solve it.
Steps to Reproduce
created my environment
conda create -n vacatures pip django=1.10.8 mezzanine
activated it(
conda activate vacatures
), went to work on my project, and when I tried running a script, it used modules from the global/base environment instead.here's a snippet of my base env list
Here's a snippet of the vacatures environment
and here's a part of the error
but django 1.10.8 does have django.core.urlresolvers, unlike django 2.0.4, which is installed in the base env.
Expected Behavior
It should only use packages and modules from the activated environment
Environment Information
`conda info`
`conda config --show-sources`
`conda list --show-channel-urls`
The text was updated successfully, but these errors were encountered: