-
-
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
"Could not find a version that matches", but acceptable version listed #2046
Comments
I've done some automated testing and it appears that this broke after 10.0.0, for the time being I'll just run the old version to work around this issue |
So the valid versions that match this specifier are: 0.2.0b3 That's it. According to pep 440 this (and anything that has a 'b' or an 'a' or whatever) is a 'prerelease'. So I'll go back to what I quoted before:
Exactly. You're not using |
That makes sense but in that case the warning should be different and specify that it's not considering the pre-releases. @techalchemy Should I create a pull request that adds an extra line about the pre-releases? Something like this perhaps:
|
@wolph The suggested change makes sense to me. Go ahead. |
I already merged a change that handles this. |
Even with that fix I still think the current message is incorrect. It says "Tried: ..." when it actually doesn't even consider them. I for one completely forgot about the |
@wolph yes the current message is still incorrect, because it isn't released yet. I don't think we need to overcomplicate this messaging too much since if it didn't install anything, technically it didn't try anything. The fact of the matter is NOTHING matched your version specifiers, so literally everything was skipped including the prereleases. |
I understand how the other fix might help a bit but I still think you'll get issues similar to this one because it's unclear why it's skipping them when they appear perfectly valid options. Looking at the code I think the change could be fairly simple: pipenv/pipenv/patched/piptools/exceptions.py Lines 11 to 23 in 2dbb8bc
|
There is a version evaluator that will tell you if it's a pre-release. I'd recommend PR'ing it up to pip-tools and then we can have @vphilippon review it there. |
Very similar to #1802 but there is a difference, I'm not using
--pre
. This issue is easily and consistently reproducible. I've tried on multiple systems.Output from
$ python -m pipenv.help
:$ python -m pipenv.help output
Pipenv version:
'11.10.0'
Pipenv location:
'/usr/local/lib/python3.6/dist-packages/pipenv'
Python location:
'/usr/bin/python3.6'
Other Python installations in
PATH
:2.7
:/usr/bin/python2.7
2.7
:/usr/bin/python2.7
3.5
:/usr/bin/python3.5m
3.5
:/usr/bin/python3.5
3.6
:/usr/bin/python3.6m
3.6
:/usr/bin/python3.6
2.7.12
:/usr/bin/python
2.7.12
:/usr/bin/python2
3.5.2
:/usr/bin/python3
PEP 508 Information:
System environment variables:
USER
LOGNAME
HOME
PATH
MAIL
SHELL
SSH_CLIENT
SSH_CONNECTION
SSH_TTY
TERM
DISPLAY
XDG_SESSION_ID
XDG_RUNTIME_DIR
LANG
LANGUAGE
SSH_AUTH_SOCK
SHLVL
PWD
OLDPWD
GOPATH
PYENV_ROOT
ANDROID_SDK
ANDROID_NDK
ROOT_DIR
TZ
PS1
ORIGINAL_PS1
RPS1
PYTHONSTARTUP
PIP_DISABLE_PIP_VERSION_CHECK
PIPENV_VENV_IN_PROJECT
SSH_AGENT_PID
LS_OPTIONS
GIT_MERGE_AUTOEDIT
WORKON_HOME
PROJECT_HOME
_VIRTUALENVWRAPPER_API
VIRTUALENVWRAPPER_SCRIPT
KEYTIMEOUT
LS_COLORS
CLICOLOR
LSCOLORS
EDITOR
HISTFILE
FZF_DEFAULT_COMMAND
FZF_DEFAULT_OPTS
_
PYTHONDONTWRITEBYTECODE
PIP_PYTHON_PATH
PYTHONUNBUFFERED
Pipenv–specific environment variables:
PIPENV_VENV_IN_PROJECT
:true
Debug–specific environment variables:
PATH
:/usr/local/bin:test///go/bin:test///bin:/usr/local/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:~/bin:test///bin:test///.fzf/bin
SHELL
:/bin/zsh
EDITOR
:vim
LANG
:en_US.UTF-8
PWD
:test
Contents of
Pipfile
('test///workspace/test/Pipfile'):Expected result
An environment with the package and dependencies installed
Actual result
Consistent warnings about not being able to find matching versions while valid versions are available.
Steps to replicate
Actual output (1500 lines): install.log
The text was updated successfully, but these errors were encountered: