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
[Windows] Python 3.6.8 environment has not been activated #8487
Comments
How did you activate it?
The warning is newer than python 3.6.7 |
But a few months ago, Python 3.6.8, a Windows installation of mine, did not have this warning.And I have run "conda activate base" in cmd and powershell and Anaconda Prompt. It seems like not work. |
It does now. You need to activate the base env like any other.
…On Wed, Apr 3, 2019, 9:56 AM Ah ! ***@***.***> wrote:
I am using conda's default base environment
How did you activate it?
when I changed to 3.6.7, there was no warning.
The warning is newer than python 3.6.7
But a few months ago, Python 3.6.8, a Windows installation of mine, did
not have this warning.And I have run "conda activate base" in cmd and
powershell and Anaconda Prompt. It seems like not work.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8487 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA_pdJbwwi_Gvr2ZGV9l2xc2WmgxB32_ks5vdF67gaJpZM4cZxrC>
.
|
Thank you for your reply. It seems that the python version released in 2019 has this warning. |
I think this warning leads to confusion. I always assumed that if I launch Python interpreter without activating any environment, it would use the If this is true - if the base environment is activated by default, then I don't understand why this warning is showing up. But if the base env is not activated by default, then |
It's not activated, conda should refuse to operate really. PRs welcome.. |
If you do not like the warning set the env var permanently. |
Which env var should I set permanently to remove the warning? |
Ah sorry, |
But be aware you'll not be properly activated and we'll be avoiding being informed of that. Conda working is a bug, other things will not. |
Basically this means that if I want to run my python code properly, I should ideally have a startup script, which would call |
or try these effectively write the wrapper script for you. |
I had the same issue. The only method that worked for me is to reinstall Anaconda and update it to the latest version. You can try this if you have nothing to lose. Best Regards, |
I just reinstalled the lastest Anaconda3 and I am still having this problem. The only way that I can run Python is to launch it from Anaconda Prompt (i.e. cmd with the base environment activated). If I run a python script or interpretter any other way, the environment is not properly configured and fails on a DLL load error if I try to load numpy or sqlite3:
Given that I have a fresh installation there must have been a pretty serious bug introduced in a recent update, as this was never a problem for me. Now it renders Anaconda pretty useless as an environment manager. Until it's fixed I'll probably switch to using virtualenv. Just to be clear, there are no spaces in the Anaconda install path: It is strange that other users don't seem to be experiencing this issue though. |
Did you read the other posts from @mingwandroid and I? You can set an env var to make it work. This isn't going to be fixed because it isn't a bug. We give you several ways to make it work:
We describe why activation is necessary in https://conda.io/projects/conda/en/latest/user-guide/troubleshooting.html#numpy-mkl-library-load-failed |
You are risking to alienate many users with such emotional responses. I think there is a clear requirement expressed by many users so far: the default conda env should be available and pre-activated any time the OS command prompt is launched. Many users (including myself) don't even use multiple environments and they simply rely on conda as a convenient packages manager. I am personally thinking of getting rid of conda and reverting to plain old python + pip. |
I'm sorry you found a harsh tone there. It was not intended. We have spent hundreds of hours fighting DLL loading issues on Windows. The options I present above are the options that we have found to work the best. Activation is important for the base environment, too. With conda 4.6, we introduced a command, That auto-activation applies to cmd.exe, powershell, and other shells, but does not affect IDEs. IDEs have been adding support for activation. FWIW, my understanding is that Microsoft's direction is to only load libraries from the immediate folder of an application. This will clear up the DLL confusion, but at great cost in efficiency. We won't support calling python.exe directly without activation, because we know that is very likely to cause problems and support issues for us. We try to guide people away from paths that we know have problems. We are always looking for a better path (something like RPATH on linux/mac), but we're not there yet. Thus, my 3 recommendations above, plus conda init, are the best we have right now. |
@msarahan I have added the CONDA_DLL_SEARCH_MODIFICATION_ENABLE environment variable as you suggested, that seems to have fixed the DLL loading issue, great! So your solutions seem to work great, thank you for explaining the problem. I understand that many users want to activate their environments manually every time, but as andy-gh said, many people just want to run in the base environment 99% of the time. Perhaps you could try and make these solutions more apparent in the docs? I previously read through this page and found no mentions of the issue or these solutions: https://conda.io/activation |
@andy-gh, I agree with you. till anconda python 3.6.6, conda works I use scite to edit and run python code on windows 7 64 bits
but no matter for fresh ( I mean I move my python 3.6.x to a U-disk) installed python from Anaconda3-2019.10-Windows-x86_64.exe or python 3.6.10 updated from 3.6.6, when I for Anaconda3-2019.10-Windows-x86_64, I have to uninstalled it, because I do not know whether there are more pacakges I have to install by hand. I miss the day that conda is an real easy-to-use tool. I have to stick to python 3.6.6( and 3.6.10 with the warning every time) and think to stop suggesting anaconda python for my classroom. |
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. |
Current Behavior
I am using conda's default base environment. The version I downloaded is 2018.12 and the default version is Python 3.7.1, so I want to change it to Python 3.6.8. But when I changed to 3.6.8, the warning environment was not activated, and when I changed to 3.6.7, there was no warning.
Steps to Reproduce
Expected Behavior
And I have activated my base environment or reboot my PC.But When I used Python version 3.6.7, the warning disappeared. On the previous computer, about a few months ago, Python 3.6.8 installed did not have this warning too.So I don't know how to do it.Plz help me.
Environment Information
`conda info`
`conda config --show-sources`
`conda list --show-channel-urls`
Thanks.
The text was updated successfully, but these errors were encountered: