Closed Mandera closed 1 year ago
Wasn't happening at first in my local windows env, I then:
pip
from 23.0.1 to 23.1pip install -e .
in generalpackager repo (Just to refresh)__editable___generalpackager_0_5_7_finder
being yielded by get_installed_modules_names()
....This is a great showcase for why
is needed
get_installed_modules_names
yielded both generalpackager
and __editable___generalpackager_0_5_7_finder
generalpackager
thereNow the question is how do we temporarily ensure we don't use the bad version in the workflow? Used to have a necessities install step
but that's now moved to a generalpackager dependency. Now the issue with that is that we need the proper setuptools before we install generalpackager
Updating to actions/setup-python@v4
from v2 might solve it
Didn't fix it. Version 56.0.0 is being used. I think this might be defined by the Python distribution which it's usually installed with, doesn't really matter though.
Let's re-instate the installing of necessities step
Seems to work!
Getting weird names from
get_installed_modules_names()
such as__editable___generalpackager_0_5_7_finder
for every editable installSeems related to external
That's also mentioning the previous issue I had in workflow