-
-
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
'save-exact' option for saving exact version in Pipfile #3441
Comments
I'm +1 on this but it requires a PEEP https://github.com/pypa/pipenv/blob/master/peeps/PEEP-000.md since it is a API change. For now, you can only edit the Pipfile manually and lock it again by |
BTW, I've just seen that you can do So there's no option so save-exact to Pipfile because it's being done already to Pipfile.lock every time you do Just my 2 cents :) |
I think that it should be by default behavior. I'm totally don't mean |
What I do to get the exact version is: pipenv run pip freeze > requirements.txt
pipenv install -r requirements.txt Just a simple workaround so, that I don't have to dig the lock file. Though it can pollute your |
|
I've looked through the docs and the cli, but cannot seem to find a way to save the version of the installed package explicitly without editing the Pipfile after installing a package.
Example:
pipenv install scipy
would addscipy = "*"
to the Pipfile.I would have expected a way to have
scipy = "==1.2.0"
to the Pipfile instead.I was wondering if this sort of functionality already exists and/or if there is any reason not to go this route.
This would be similar to running
npm install react --save-exact
, where the installed version is added to thepackage.json
file.Apologies in advance if this is not the right forum/format for this question. I had tried looking through the docs, Stackoverflow, and search engines without luck.
The text was updated successfully, but these errors were encountered: