As a first response to overcoming Viktor's problem, 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. (Sorry, Felix, I hate to suggest more work for you!). 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.
This way, a user could follow the suggestion in the warning message from pip by creating a venv and installing Leo into it. On Friday, December 29, 2023 at 8:52:13 AM UTC-5 Thomas Passin wrote: > On Friday, December 29, 2023 at 8:49:18 AM UTC-5 Edward K. Ream wrote: > > On Fri, Dec 29, 2023 at 7:35 AM Thomas Passin wrote: > > > I may be one of the few people who realizes how inconsistent the > installation situation is because I run around 8 or 10 different distros > and distro versions from time to time to make sure a certain software > package runs right on Linux. > > I'm glad we have you as our resident guru. > > > Far from a guru! I suppose I'm not really a newbie any more, but I'm > still stumbling around. > -- 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/f9fb1f3e-f384-40c6-82d4-b36a927e815dn%40googlegroups.com.
