-
-
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
Wildcard version dependency pins wildcard instead of specific version #4278
Labels
Type: Bug 🐛
This issue is a bug.
Milestone
Comments
Updated with minimal steps to reproduce. |
The problem is in Lines 1186 to 1197 in b5becd8
Looks like this was introduced by 552d127, which activated the (unused) changes made much earlier in a08a2da. |
2 tasks
2 tasks
frostming
added a commit
that referenced
this issue
May 29, 2020
#4278: Don't pin wildcard versions in lockfile
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Spun off from #4263. This is a regression from 2018.11.26.
Issue description
Dependencies with wildcards get locked with a wildcard version instead of a specific version.
Steps to replicate
pipenv install 'example-test-package==1.0.*'
Expected result
Pipfile.lock contains:
Actual result
Pipfile.lock contains:
The text was updated successfully, but these errors were encountered: