Skip to content
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

Packages -> Virtualenv -> [virtualenv_name] doesn't have any apparent effect? #28

Open
posita opened this issue Apr 23, 2015 · 1 comment

Comments

@posita
Copy link

posita commented Apr 23, 2015

I can change virtualenvs successfully from the status bar, but choosing Packages -> Virtualenv -> [virtualenv_name] doesn't seem to have any effect. I'm on OS X 10.9.5:

Darwin ... 13.4.0 Darwin Kernel Version 13.4.0: Wed Mar 18 16:20:14 PDT 2015; root:xnu-2422.115.14~1/RELEASE_X86_64 x86_64

How to reproduce:

  1. Start Atom
  2. Create a new file (e.g., foo.py)
  3. Note <None> appears for the virtualenv in the status bar
  4. From the application menu, choose Packages -> Virtualenv -> [virtualenv_name]

<None> continues to appear in the status bar. Further if a package like autocomplete-plus-python-jedi (or linter-pyflakes, linter-pylint, etc.) is installed, it will not look for Jedi in the virtualenv (but rather whatever environment was configured at the time Atom was started).

Compare to:

  1. Start Atom
  2. Create new file (e.g., foo.py)
  3. Click on <None> in the status bar and select [virtualenv_name]

Now the status bar is updated to [virtualenv_name], and autocomplete-plus-python-jedi will find Jedi in the virtualenv.

@posita
Copy link
Author

posita commented Apr 23, 2015

Packages -> Virtualenv -> Deactivate does seem to reset the status bar to <None>, however. 😕

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant