Closed AlexanderMishutkin closed 2 years ago
This can break installation of requirements if you install them from any other directory except project root directory
It works fine.
For example this command works correctly:
$> python3.6 -m pip install -r clouni/requirements.txt
It returns:
Looking in indexes: https://test.pypi.org/simple/
Requirement already satisfied: netaddr==0.7.19 in ./clouni-venv/clouni/lib/python3.6/site-packages (from -r clouni/requirements.txt (line 1)) (0.7.19)
Requirement already satisfied: pyyaml in ./clouni-venv/clouni/lib/python3.6/site-packages (from -r clouni/requirements.txt (line 2)) (5.3)
Requirement already satisfied: six in ./clouni-venv/clouni/lib/python3.6/site-packages (from -r clouni/requirements.txt (line 3)) (1.16.0)
Requirement already satisfied: cotea==1.3.2 in ./clouni-venv/clouni/lib/python3.6/site-packages (from -r clouni/requirements-cotea.txt (line 2)) (1.3.2)
As you can see pip
restores the correct path clouni/requirements-cotea.txt
even though in the requirements.txt
there is only ./requirements-cotea.txt
PS
Maybe your bug happened because you used short form pip
, I can not check whether pip
works properly on my pc. Can you provide logs?
But it is officially recommended to use python -m pip
.
Chain all requirements, so no double pip install call is needed.
No pull requests for 2 months. So I decided to revive the party...