package not checked out?

We are using actions/checkout@v2 for many of the submodules in PySAL with varying success. For example, in spaghetti using actions/checkout@v2 in unittests.yml runs smoothly without issue. However, in tobler using actions/checkout@v2 in unittests.yml we are getting a ModuleNotFoundError: No module named 'tobler'. I am wondering if I can get any insight as to why this is happening in tobler but not spaghetti, or if there is something we are doing obviously wrong. I tried the GitHub Community Forum’s Actions Board first, but got a “missing page” there.

[knaaptime]

But doing this negates the purpose of using actions/checkout@v2. From the docs:

This action checks-out your repository under $GITHUB_WORKSPACE, so your workflow can access it.

i dont follow… the purpose of the action is to check out, but checking out just means cloning the repo so that the source code is available, it doesnt actually install the package unless you explicitly ask it to (and the action can be used by lots of other repos that arent python packages, so it’s definitely not supposed to install)

i have no idea why the other packages work without that step, but i think the action itself is working as intended

[jGaboardi]

@ericsciple I am wondering if it would be possible to get some clarification on the need for run: pip install -e . --no-deps --force-reinstall in some repos (e.g. pysal/tobler), while others are fine without it (e.g. pysal/spaghetti). It seems that something is happening differently in these two cases (though I am quite possibly incorrect), but I can’t pin down what exactly it is. It may not even be happening in actions/checkout, but I haven’t been able to determine that for sure.