Skip to content

Missing python3.x executable due to preferred usage of venv #282

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.

Sign up for GitHub

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

Jump to bottom
Closed
neverland4u opened this issue Sep 12, 2018 · 0 comments
Closed

Missing python3.x executable due to preferred usage of venv #282

neverland4u opened this issue Sep 12, 2018 · 0 comments

Comments

@neverland4u
Copy link

neverland4u commented Sep 12, 2018 •
edited
Loading

pyenv-virtualenv will prefer venv instead of virtualenv when creating virtual env for Python 3.x.

But venv won't create python3.x link file while virtualenv would create it.

Thus, python3.x --version won't work on current version, which leads problems of jedi/other usages of the aforementioned command.

Pls consider add python3.x link after venv call.

Many thx.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yyuu @neverland4u