To ease development and testing of Software Heritage modules, we should somehow provide our packages as pip modules.
- An approach which mangles our requirements-swh.txt to use git repositories only works well for the first level of dependencies and breaks down when you try to install the second level of dependencies using the original requirements files.
- Approaches cloning the full environment and setting the PYTHONPATH to add all modules are prone to version clashes between the module being tested and the full environment
- Finally, it'd be nice to get closer to regular "upstream" python processes, which will make new contributor onboarding easier
A tractable approach for this seems to be using DevPI, https://devpi.net/, a private python module index and cache server.