Page MenuHomeSoftware Heritage

Add support to not install the dev modules in editable mode
ClosedPublic

Authored by vsellier on May 5 2021, 1:06 PM.

Details

Summary

It's needed by the ci to be able to reference the api links

Related to T3307

Diff Detail

Repository
rDDOC Development documentation
Branch
master
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 21281
Build 33045: arc lint + arc unit

Event Timeline

If I recall correctly, without using the -e option of pip, some swh packages end up installed from pypi by dependencies transitivity.

For the sphinx-dev tox target, we want to use the local state of each swh package so the use of -e to force that fact.

So not sure that's the best solution here.

If I recall correctly, without using the -e option of pip, some swh packages end up installed from pypi by dependencies transitivity.

For the sphinx-dev tox target, we want to use the local state of each swh package so the use of -e to force that fact.

So not sure that's the best solution here.

@vsellier, in fact I got mistaken by the sphinx warning below that I thought having fixed but it is still there:

/home/anlambert/swh/swh-environment/swh-docs/docs/swh-core/cli.rst:3: WARNING: Definition list ends without a blank line; unexpected unindent.

I thought using -e option will use package state after the last tag but it is already the case when you install a package from its local path.

So you are right, the solution is to remove the -e option of pip.

Makefile.local
-1–5

You can remove this and simply remove the -e option of pip.

Makefile.local
-1–5

great, I thought it was useful for local runs

vlorentz added inline comments.
Makefile.local
-1–5

I believe @anlambert meant this:

ifeq ($(PIP_INSTALL_EDITABLE),yes)
PIP_INSTALL_OPTIONS="-e"
endif

But I'd rather keep it explicit

Makefile.local
-1–5

Nope, we can simply drop the use of -e. It was a mistake of mine.

completely remove the -e option

Thanks !

And I think that I found how to fix the last remaining warning cited above.

This revision is now accepted and ready to land.May 5 2021, 2:30 PM

And I think that I found how to fix the last remaining warning cited above.

good news ;)
thanks