'save-exact' option for saving exact version in Pipfile
See original GitHub issueI’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 add scipy = "*"
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 the package.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.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:9
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Basic Usage of Pipenv - Read the Docs
Specify your target Python version in your Pipfile 's [requires] section. Ideally, you should only have one target Python version, as this is...
Read more >How to specify platforms-specific extras or version in Pipfile?
It's not clear what to do when one wants to specify different version or options for a package, depending on the platform. Specifically,...
Read more >How to save exact npm package versions
There are two ways to force npm or yarn to save exact versions in your package.json. 1. Everytime you install a package //...
Read more >Pipenv - Easily Manage Packages and Virtual Environments
In this Python Programming Tutorial, we will be learning how to use Pipenv. Pipenv is a new package manager that combines pip and...
Read more >Python Dependencies - Everything You Need to Know
Creating a lock file (such as pipfile.lock) ensures that dependencies remain pinned to the exact version in use, ensuring reproducibility.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think that it should be by default behavior. I’m totally don’t mean
any
version when I install something, but I meanthe latest on the current moment
(moment when I usepipenv install smth
). And I wish bugfixes to be applicable so it should be not==
but~=
pipenv sync
installs the versions from the lock file, andpipenv install
re-lock with the Pipfile specifiers and then installs that updated lock file.