Hello Thomas, [email protected] schrieb am Samstag, 12. Oktober 2024 um 14:42:04 UTC+2:
I understand log 003 well enough. The standard-issue Leo install is being executed instead of the one in your clone repo. How do you start Leo normally, e.g., for log 001? [user@fedora-leo-study-vm ~]$ cd PyVE/GitHub/Leo/ [user@fedora-leo-study-vm Leo]$ source bin/activate (Leo) [user@fedora-leo-study-vm Leo]$ cd leo-editor/ (Leo) [user@fedora-leo-study-vm leo-editor]$ python -m leo.core.runLeo & I think the restart-leo command has a weakness - it's going to start Leo using a shell inheriting its owner's environment. If that original environment doesn't include a PYTHONPATH variable or hasn't been cd'ed to the leo-editor directory, it will find the pip-installed version instead of the git version. My environment does not include a PYTHONPATH variable - but - as you can see above I am starting Leo from the leo-editor directory ... I just tried the restart-leo command in one of my Linux VMs. It's also running in a venv. The restart worked as intended. however, I start Leo with the git repo clone version of Leo by using a shell script that firsts sets PYTHONPATH to point to the leo-editor directory in my git repo. Then it sources the venv. So when the restart-leo command runs, the new shell inherits the right environment. If this is right, the command will be unreliable for anyone who doesn't start the original Leo session the "right" way. The user might not even notice they are running the wrong version of Leo. ... Let's see, what Edward thinks about this issue / problem ? Thanks a lot for your detailed explanation ! With kind regards, Viktor -- 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/ebd70cf0-9583-4100-acd3-653c7e78d195n%40googlegroups.com.
