On Saturday, 21 March 2020 07:32:11 UTC-7, tfer wrote:
>
> I been running Leo from a local clone of 'develop' under full Anaconda,
> (not using env's, just adding things it complained about missing to the
> base site packages). I've since gone to a miniconda base and created a
> conda env 'leobase'. At some point playing with getting this barebones env
> to work, I found out what setup.py is for and realized I should be letting
> it handle this.
>
> Running:
>
>> ./setup.py develop
>
>
It's prefered to use `pip install --editable path\to\code` over `python
setup.py develop`. It has a handler for the dependencies needed just for
setup (setup janitor in this instance). More importantly it registers the
installed files so they can removed later with `pip uninstall {thing}`.
With the `develop` method it's up to you to hunt down all the instances
under PYTHONHOME site-packages, scripts, etc. and remove them. See
https://stackoverflow.com/questions/30306099/pip-install-editable-vs-python-setup-py-develop
-matt
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/5d0eb8e8-7acc-47e2-aff5-f90d9fc1d726%40googlegroups.com.