On new instance of Atom, virtualenvs don't show

[yuanchueh]

I have a consistent issue where when I load atom, my virtualenvs list is empty. If I un-check get virtualenvs from home folder and re-check then the virtualenvs show in the list. It's almost something I have to do everytime I launch atom to get my list of virtual envs.

I also have listed and tried variations of:
WORKON_HOME=~/.virtualenvs (I'm on Ubuntu).

Additional is blank.

[thmsklngr]

Hi,

I have about the same problem, but in my case I even can't create a virtualenv, even though the wrapper is in the path variable and available. Working on Windows with the latest Atom version.

Regards, Thomas

[yuanchueh]

I create and manage my virtualenvs from terminal.

[KennethEnevoldsen]

I have the exact same issue.

[pghilardi]

Hi @KennethEnevoldsen , are you still facing this problem?

Now I am with some time to fix bugs in this package and I am returning to maintain it.

[KennethEnevoldsen]

Sounds Good! Yes I still have the issue

[pghilardi]

@KennethEnevoldsen , could you give me more information about your env?

Windows or Linux (which distro)?
Can you enumerate the steps? Just open Atom and the envs are not there?
Are you using virtualenv inside the home folder or on specific paths?

Thanks

[KennethEnevoldsen]

Yes, it is on the latest version of MacOS Mojave,
When I open the Atom the envs are simply not there, but unchecking/checking it off in pref. seems to solve the issue.
The virtualenv (or rather the python installations) are located:
/Users/foo/.virtualenvs/venv/bin/python
Where foo is the user name and venv is the name of a certain virtual environment

[pghilardi]

Thanks!

I am trying to reproduce the problem on Ubuntu without success. I am investigating how to guarantee that the envs are loaded on Atom start. I'll let you know when I have a new version that you can test.

[KennethEnevoldsen]

I will look further into it if you like, when I have my computer again, however currently won't have access to it for the following week. However, I think on of the issues is caused by the fact that I have multiple pythons installations (anaconda as well as using homebrew). It does detect the anaconda environments at the very beginning.