Question: generate requirements.txt without locking all package versions
See original GitHub issueGeneral question: how can I generate requirements.txt that specifies only the minimal versions as in the Pipfile lock? It is, if Pipfile contains "*"
I’d like requirements.txt to allow any version of a package.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
How to create requirement.txt without all package versions
Generally sometime when we are creating new project, we need to install latest packages(modules) so it good idea to keep all package names( ......
Read more >Why requirements.txt isn't enough - model.predict
Not having these versions locked down means that running pip install -r requirements.
Read more >Python pip requirements.txt lock file
The short answer is python has no concept of lock files, equally it can be argued python has no package dependency files at...
Read more >Commands | Documentation | Poetry - Python dependency ...
This command locks (without installing) the dependencies specified in pyproject.toml . Note. By default, this will lock all dependencies to the latest available ......
Read more >pipenv Documentation - Read the Docs
Makefile, direct calls to pip and python -m venv or virtualenv. to create virtual ... By default pipenv lock will lock all known...
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 FreeTop 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
Top GitHub Comments
I thought a bit about how this would be implemented, and it occurs to me that you probably need to come up with a verb for this operation. This would involve some design decisions and probably needs to be approved by Kenneth, maybe via a PEEP?
This is accomplished by the new
pipenv requirements
command.