-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
ValueError: Not a valid python version #3241
Comments
Hey @Mortuie, We did a quick check and this issue looks very darn similar to
This could be a coincidence, but if any of these issues solves your problem then I did a good job 😄 If not, the maintainers will get to this issue shortly. Cheers, |
@frostming I have installed on linux using the update-vendor branch and it doesn't fix the error, the error still persists... |
Running into the same issue here (Ubuntu 18.10), so I did a quick poke-around with It seems as though the /usr/bin/python2.7 binary on 18.10 has made the odd decision to report its version as '2.7.15+'. This trips up the vendored The invalid version string then causes an exception to be raised by This feels to me like a mistake made while packaging this version of I'm guessing the "correct" thing to do here would be for |
We understand the issue in full, it's being tracked in pythonfinder already -- sorry for the trouble and thanks for the report |
This was fixed in #3254 -- sorry for the trouble |
AVOID POSTING ISSUES UNDER THIS CATEGORY.
If Pipenv is not functioning as you would like it to, consider filing either a bug report, or a feature request instead.
Please refer to StackOverflow tag for more information.
Please run
$ pipenv --support
, and paste the results here. Don't put backticks (`
) around it! The output already contains Markdown formatting.If you're on macOS, run the following:
If you're on Windows, run the following:
If you're on Linux, run the following:
Well I can't even run pipenv --support it gives me this error
I'm using pyenv and pipenv and they don't seem to be playing nice, anyone seen an error like this before ?
The text was updated successfully, but these errors were encountered: