Also someone suggested http://stackoverflow.com/questions/3667238/how-can-i-get-the-file-system-location-of-a-powershell-script/3667376#3667376 helps.

Honestly just adding those scripts to the distribution seems to work flawlessly on win7-64bit. Would you like a PR for this?

Sure, but see also #913

Ahh, seems like that deals with it all much more nicely. Thanks for the ref.

Will #913 work in Powershell? If not, would it be worth just adding the ps scripts to the distribution?

Is there anything bad about just including ps scripts while you figure out #913 ? I thought conda was supposed to be advertised as more featureful than virtualenv :P

Just to chime in, I also wasted about an hour of time figuring out why my environments weren't activating.

Anaconda envs are advertised as full-featured replacements for venv, so I would expect Powershell support.

If @Liquidmantis or anyone else wants to submit the ps scripts that @rossant mentioned, I'll merge them. It would be nice to not include another license file with Conda. I the meantime, we are reviewing #913 and its newer derivatives and hope to merge it soon.

I'm fine with them being added, and was going to submit a PR now, but it looks like conda has been reworked and the old bat files have been removed anyway so I'm not sure how to proceed.

Things are in a little bit of flux right now. The activate scripts were moved out of conda, into conda-env. This has unfortunately made the activate scripts harder to test, since they effectively depend on two packages. We will be discussing this after the Anaconda 2.4.1 release, and hopefully coming up with a better arrangement. If you put a PR in against conda-env, we'll be happy to consider it, and we'll take care of any moves necessary thereafter.

@msarahan It looks like the Anaconda 2.5 release is out now. Has there been any progress on this? It would greatly improve the Windows UX if this could be fixed. 🙏

@Liquidmantis Seems like the old bat files have been added back. I just tested your scripts from pscondaenvs and they work with conda 4.0.5.

#913 was closed in favor or #1727, but it didn't address the powershell issue.
@msarahan would you still accept the pr if @Liquidmantis or anyone else submits them?

Sorry for the delay here. Absolutely.

Before they are accepted, they need to pass the test_activate.py tests. I added a bit of scaffolding for powershell, but didn't want to bloat #1727 any further. Please see this comment for how to run the tests with the new shell (modify test_activate.py, but also pass a command-line argument): #1727 (comment)

Ping me if you are working on this and need help.

@msarahan just took a look at this today to get it added. Might take me a bit to implement the Powershell test. Just noticed that the section on it is just an exception :person_frowning:

@vmuriart go ahead with a PR whenever, even if tests are not passing. I'll be happy to help you flesh out the framework.

+1, encountering this issue on windows 10.

+1 again, just ran into this again trying to do Py3 testing.

Addressed with #3175 and #3960

Is there any progress on this? just tried https://github.com/Liquidmantis/PSCondaEnvs, but they break
and executing activate.bat within powershell just hangs forever

Same here - I'm very confused about the lack of working PowerShell support.

If anyone following this thread would like to contribute, #6471 sketches out the start of what a powershell wrapper might look like under the conda 4.4+ framework. The #6471 PR has additional instruction and comments. A new PR that follows the same patterns established by the five other shell wrappers, and as sketched out in #6471, would be very welcome.

bump desperately seeking Powershell support

Resolved by #7794. Will be included in conda 4.6.

This is still messed up with Powershell with current anaconda version.

@mingwandroid Any progress? I recently downloaded anaconda 5.3, but activate is still not working with ps. Or is there some trick?

It'll be part of conda 4.6 I think. I cannot give a reliable timeline for that at present though, sorry.

https://www.anaconda.com/blog/developer-blog/conda-4-6-release/

Looks like it made it in

https://www.anaconda.com/blog/developer-blog/conda-4-6-release/

The link is broken. Here's the working one https://www.anaconda.com/conda-4-6-release/

Still, great job, guys!

Correct me if I'm wrong, with the current solution (conda 4.6) an instance of python runs at startup of any Powershell process querying for the active environment, and its name is printed at the beginning of the prompt. This does not seem optimal because it slows down the loading of the shell even if the user is not interested in actually working with conda. The implementation in cmd seems to be better because conda runs only when actively requested by the user (via conda activate) and information about the environment disappears when no longer needed (deactivate). Shouldn't it behave in the same way in Powershell?

@giuliofoletto I think it would be better if you opened up a new issue for discussing possible enhancements to the current implementation of this. Having a new, open issue should help with visibility of your concerns.

Conda version: conda 4.6.11
Windows 10

Looks like the conda activate <new_env> is actually still pointing to the base environment.
And if you install new packages, assuming that you are actually installing in the new_env, it will install in the base env. So, please beware!

e.g. I did the following:
1.
conda env list >>
base * C:\Users\abcd\AppData\Local\Continuum\anaconda3
envp3 C:\Users\abcd\AppData\Local\Continuum\anaconda3\envs\envp3

conda activate envp3
conda env list >>
base * C:\Users\abcd\AppData\Local\Continuum\anaconda3
envp3 C:\Users\abcd\AppData\Local\Continuum\anaconda3\envs\envp3

conda install -c conda-forge tldextract >>
environment location: C:\Users\abcd\AppData\Local\Continuum\anaconda3
That is, it is installing in my base env.

Another issue:
If I do conda init powershell>>
then restarting my powershell, ps is getting initialized with base env. Now if I want to activate envp3, it is crashing. same with deactivate.

Let me know if I am doing anything wrong.

Having the same issue on Win10 with powershell after running conda init powershell. Conda 4.6.11 as well.

https://github.com/Liquidmantis/PSCondaEnvs. No longer supports.

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.