Skip to content

pipenv and vscode-python not working #2381

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

Closed
laoshaw opened this issue Aug 13, 2018 · 2 comments
Closed

pipenv and vscode-python not working #2381

laoshaw opened this issue Aug 13, 2018 · 2 comments

Comments

@laoshaw
Copy link

laoshaw commented Aug 13, 2018

Running vscode 1.25.1 on ubuntu 16.04 64bit with newest vscode-python.

  1. if I switch to a folder contains Pipfile(Ctrl-K, Ctrl-O), vscode will not pick up the Pipefile at all, the terminal(ctrl + `) will show python from the OS, not from pipenv. If I open vscode from a pipenv directory without running 'pipenv shell' it's still the same, vscode ignores pipenv totally.

  2. if I start vscode from within a pipfile directory after running 'pipenv shell', vscode's own terminal still not show pipenv's executables, the PATH still has /usr/local/bin put ahead of pipenv's own virtualenvs PATH

To me, vscode-python + vscode + terminal do not work

@brettcannon
Copy link
Member

It sounds like you either have not created a virtual environment yet for your project using pipenv, you haven't selected the virtual environment as your interpreter, pipenv isn't being found on your PATH, or executing pipenv is failing because of how you set LC_ALL/LANG isn't coming through to VS Code as required by pipenv/click (not sure as you didn't fill out the issue template which asks for key details to help figure this out).

Try this all out and if you're still having issues please open a new issue with the issue template filled out.

@d3r3kk
Copy link

d3r3kk commented Aug 13, 2018

Please also see other Pipenv-related issues in our backlog, you are potentially reporting a duplicate. You can add your thumbs-up vote to any of those, or add to the conversation to help us out. (Also, we have an issue to improve virtual env identification in #2288)

@lock lock bot locked as resolved and limited conversation to collaborators Sep 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants