Resolve version requirement error

• Describe the issue briefly here:

Pipenv can’t correct resolve version requirement with suffix like: eth-keys>=0.2.0b3,<1.0.0

• Please run $ python -m pipenv.help, and paste the results here.

$ python -m pipenv.help output

Pipenv version: '2018.05.18'

Pipenv location: '/usr/local/lib/python2.7/site-packages/pipenv'

Python location: '/usr/local/opt/python@2/bin/python2.7'

Other Python installations in PATH:

• 2.7: /usr/local/bin/python2.7

• 2.7: /usr/local/bin/python2.7

• 2.7: /usr/bin/python2.7

• 3.6: /usr/local/bin/python3.6m

• 3.6: /usr/local/bin/python3.6

• 2.7.15: /usr/local/bin/python

• 2.7.10: /usr/bin/python

• 2.7.15: /usr/local/bin/python2

• 3.6.4: /usr/local/bin/python3

PEP 508 Information:

{'implementation_name': 'cpython',
 'implementation_version': '0',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '17.5.0',
 'platform_system': 'Darwin',
 'platform_version': 'Darwin Kernel Version 17.5.0: Fri Apr 13 19:32:32 PDT 2018; root:xnu-4570.51.2~1/RELEASE_X86_64',
 'python_full_version': '2.7.15',
 'python_version': '2.7',
 'sys_platform': 'darwin'}

System environment variables:

• RUSTUP_DIST_SERVER
• GOPATH
• LESS
• RUSTUP_UPDATE_ROOT
• http_proxy
• LC_CTYPE
• TERM_PROGRAM_VERSION
• LOGNAME
• USER
• NVM_DIR
• HOME
• PATH
• ZSH
• TERM_PROGRAM
• LANG
• TERM
• Apple_PubSub_Socket_Render
• https_proxy
• SHLVL
• SECURITYSESSIONID
• XPC_FLAGS
• RBENV_SHELL
• EDITOR
• NVM_CD_FLAGS
• TERM_SESSION_ID
• XPC_SERVICE_NAME
• SSH_AUTH_SOCK
• SHELL
• PYTHONDONTWRITEBYTECODE
• LC_ALL
• PIP_PYTHON_PATH
• _
• TMPDIR
• LSCOLORS
• OLDPWD
• HOMEBREW_GITHUB_API_TOKEN
• __CF_USER_TEXT_ENCODING
• PWD
• PAGER
• NVM_RC_VERSION

---

Expected result

version 0.2.0b3 should be installed

Actual result

Requirements file provided! Importing into Pipfile…
Pipfile.lock not found, creating…
Locking [dev-packages] dependencies…
Locking [packages] dependencies…

Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
Could not find a version that matches eth-keys<1.0.0,>=0.2.0b3
Tried: 0.1.0b1, 0.1.0b1, 0.1.0b2, 0.1.0b2, 0.1.0b3, 0.1.0b3, 0.1.0b4, 0.1.0b4, 0.2.0b1, 0.2.0b1, 0.2.0b2, 0.2.0b2, 0.2.0b3, 0.2.0b3

Steps to replicate

Prepare a requirements.txt, content below: eth-keys>=0.2.0b3,<1.0.0

Run pipenv install -r requirements.txt, will cause output error messages

Run pipenv run pip install -r requirements.txt, success.

[uranusjr]

Thanks! It looks like the problem may be related to #1802. Can you try the solution mentioned in it and see if it fixes the problem?

(Thinking out loud: This --pre can be a bit unfriendly to users sometimes. Perhaps we can infer it sometimes from the Pipfile? In this case, for example, the user clearly is dealing with prereleases since it is already in the constraints. Maybe we can just supply the flag automatically.)

[uranusjr]

Indeed, we just added a hint to mention the --pre flag, but the behaviour still leaves much to be desired ergonomically. We will certainly look into how we can make it feel more natural.