venv-update doesn't allow for bootstrap requirements to also be declared in requirements-dev.txt
See original GitHub issuerequirements-tools isn’t aware of requirements-bootstrap.txt
and can generate requirements files that include things already declared in requirements-bootstrap.txt
. e.g. pre-commit->importlib-resources->wheel, where wheel
is needed for bootstrapping.
venv-update
will fail to install because “Double requirement given”.
- Removing
wheel
fromrequirements-bootstrap.txt
makesrequirement-tools
happy but it meansvenv-update
doesn’t necessarily have the rightwheel
installed before continuing to install rest of requirements. - Removing
wheel
fromrequirements-dev.txt
causescheck-requirements
to fail. That tool is valuable to ensure requirements are completely declared and pinned
Issue Analytics
- State:
- Created 5 years ago
- Comments:7
Top Results From Across the Web
What's the proper way to install pip, virtualenv, and distribute ...
Install virtualenv into a bootstrap virtual environment. Use the that virtual environment to create more. Since virtualenv ships with pip and distribute, ...
Read more >Setting Up Your Python Environment With Venv ... - Frank's Blog
As you add, update, and remove packages, you can run that command again to update your requirements.txt file. Installing From Your requirements.
Read more >Python Virtual Environments: A Primer
In this tutorial, you'll learn how to work with Python's venv module to create and manage separate virtual environments for your Python ...
Read more >pipenv Documentation - Read the Docs
Automatically generates a Pipfile, if one doesn't exist. ... You can also specify $ pipenv install -r path/to/requirements.txt to import a requirements file ......
Read more >Working with the AWS CDK in Python
This strategy makes updating your dependencies simpler. You can edit requirements.txt to allow upgrades; simply replace the == preceding a version number with ......
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
If you upgrade to
importlib-resources==1.0.2
I’ve fixed the dependence onwheel
I’ve confirmed this is not a
venv-update
issue but to do with tox-pip-extensions. Here are the files I’m using to set up repro, with updated pip and venv-update versions:venv-update
works correctly. Note that it installswheel==0.26.0
during bootstrap, then upgrades towheel==0.33.1
when installing requirements. Which is exactly what we want (bootstrap requirements independent from application requirements), therefore the use case I mentioned earlier is already handled properly and this issue is invalid.I was able to reproduce issue under tox environment, I’ll open a ticket on tox-pip-extension and take discussion there.