openoms urged this repair on Telegram to maintain utilizing pip:
sudo rm /usr/lib/python3.*/EXTERNALLY-MANAGED
Christian Decker added some context round Core Lightning’s use of Python in its construct course of:
Python shouldn’t be a runtime dependency, which is why it isn’t
being listed as a direct dependency, however we use it for a wide range of
construct steps. The error you acquired is as a result of the pip atmosphere is
owned by root because you put in it by way of the bundle supervisor. In the event you
wish to set up the construct dependencies we strongly recommend utilizing a
virtualenv. Steps on the way to set that up rely on the OS, and your
Python setup, therefore why it’s left undocumented (it isn’t CLN
particular, and any documentation on the way to create virtualenvs would
bitrot, and we will not be authoritative anyway, since it’s an exterior
mission). We simply must discover a good level to chop off the lengthy tail,
and for venv that was the place that felt proper.Python dependency administration grew fairly organically, which explains the mess of various concepts and fashions being combined. Often you will have the system atmosphere, which you’ll be able to prolong by means of a person atmosphere that will get overlaid. This doesn’t work nevertheless if a person bundle clashes with a system bundle. We appear to depend on somewhat latest bundle variations, that will conflict, inflicting this error. A virtualenv (initialized with
--no-site-packages) creates a clean web page with out bizarre combos of system and person packages.
