How should we identify dependencies?

Hi @ofek

Thanks again for this magnificent project! I have a quick question, which is, how are we suppose to track requirements?

I noticed the requirements.txt file is a little different than I’m used to seeing:

(venv) my-computer:tests blong$ cat requirements.txt 
-e .

I also noticed, I can install pip dependencies using hatch, like so:

(venv) my-computer:tests blong$ hatch install opencv-python
Installing...
Collecting opencv-python
  Using cached opencv_python-3.3.0.10-cp36-cp36m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl
Collecting numpy>=1.11.1 (from opencv-python)
  Downloading numpy-1.13.1-cp36-cp36m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl (4.5MB)
    100% |████████████████████████████████| 4.6MB 324kB/s 
Installing collected packages: numpy, opencv-python
Successfully installed numpy-1.13.1 opencv-python-3.3.0.10

Does this mean I am supposed to track dependencies (for now) using pip freeze > requirements.txt or is there some better process?

[malarinv]

Any update on this?

[nlhkabu]

As this ticket is blocked by the development of pip’s dependency resolver https://github.com/pypa/pip/issues/988, I thought I would mention here that the pip team is looking for help from the community to move forward on that subject.

We need to better understand the circumstances under which the new resolver fails, so are asking for pip users with complex dependencies to:

1. Try the new resolver (use version 20.1, run --unstable-feature=resolver)
2. Break it 😛
3. File an issue

You can find more information and more detailed instructions here

Thanks!