LeoInteg should support connecting to Leo running in a venv

[ranvik14]

The problem was described in this message on Leo's google group:

• https://groups.google.com/g/leo-editor/c/rPWY2AxO7cE/m/a-114jfTAAAJ

In a follow-up msg in the same thread a possible solution was described by TBP - See

• https://groups.google.com/g/leo-editor/c/rPWY2AxO7cE/m/C-Juy9fjAAAJ

@boltex : For simple access here's the text of the proposed solution:

"""I suggest that Felix could find a way to have LeoInteg open a venv and launch Python from that. This would require a new setting that would take priority over the current setting for the Python executable. Leo integ would have to run the venv activation script and launch the bridge in that environment. I don't know how to do that but I imagine it's possible. Once launched, LeoInteg would not need to know about the venv any more to communicate with the bridge."""

In a follow-up comment I'll describe how I am using pip & venv to install Leo from PyPI.

[ranvik14]

In all my Linux VMs - either Debian or Fedora based - I'm always using Python's virtual environments in the same way:

• I have a directory 'PyVE' in my home directory with two sub-direcories:
• -> Directory # 1 - called ' GitHub' - holding the latest version of 'https://github.com/leo-editor/leo-editor/blob/devel/README.md' - while -
• -> Directory # 2 - called 'PyPI' - is holding the latest stable version of Leo released at PyPI.

For '~/PyVE/PyPI' I use the following ~ activation ~ steps:

• cd ~/PyVE/PyPI/Leo
• source bin/activate
• leo &

[boltex]

@ranvik14 Thank you for entering this issue.

I'll take a deeper look into it right after I finish LeoJS 1.0.