Page MenuHomeSoftware Heritage

Provide a pip-compatible index of python modules
Closed, WontfixPublic

Description

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.

Event Timeline

olasd created this task.Apr 17 2018, 4:43 PM
olasd triaged this task as High priority.
zack added a subscriber: zack.Sep 17 2018, 10:58 AM

now that T1193 is out of the door, i'm adding it a note about the need of updating the getting started doc when this is done

Not sure this task is still really needed, now we are about to publish swh's python packages on pypi...

olasd added a comment.Oct 8 2018, 3:10 PM

Not sure this task is still really needed, now we are about to publish swh's python packages on pypi...

Probably not; the only thing that would be useful on a private PyPI index would be to be able to publish dev packages with the contents of master (and do testing when we break APIs), but we can do that on the main PyPI just as well.

zack closed this task as Wontfix.Oct 8 2018, 3:22 PM