Problem w/ venv's on Windows 10

[dstrozzi]

This is a thread I posted on the elpy github, user galaunay was quite helpful but we couldn't figure it out. He suggested I post it here, so there I am. I'll just link to the old thread:

jorgenschaefer/elpy#1628 (comment)

[jorgenschaefer]

Hello and thanks for the report! I'm afraid this is tricky to address … Windows uses virtualenvs, just "a little bit different" than Unix. And Anaconda also uses virtualenvs, just "a little bit different" than normal Python. I have neither Windows nor Anaconda here, so I can't really reproduce this :-(

If you find out what the problem is, or anyone else, please let me know!

[dstrozzi]

Well, a year later I am trying to revisit this. In case you're interested, I started an SO question:
https://stackoverflow.com/questions/63862190/using-numpy-in-anaconda-python-running-in-emacs-on-windows

[dstrozzi]

OK here's a glimmer of hope. I started cmd.exe (the good old DOS shell), did "conda.bat activate", then started emacs from that CMD session. And, I can load numpy! AND "from pylab import *" works too! But figure windows don't work - the original old problem. But progress.

[acimmarusti]

@dstrozzi it's been a while. Did you solve this issue?
It's definitely affecting me, and I can see this issue #113 being clearly related.

[dstrozzi]

Good to hear from someone on this! I have largely given up on trying to use python within emacs on Windows. In the various Venn diagrams of workflows, it seems like this is a set of measure zero. But, I am willing to try revisiting it together. Stay tuned.