Hello Thomas, tbp1...@gmail.com schrieb am Freitag, 29. Dezember 2023 um 00:54:50 UTC+1:
You referring to needing to use *--break-system-packages*, is that right? Yes. I don't see this as a Leo issue. It is an issue between 'LeoInteg' & 'Leo', if the underlying Linux distro has adopted PEP 668. This is why addressed both Felix - and - Edward in my initial feedback - but - obviously failed to provide the necessary additional context / information ... You are installing Leo into the system's Python install, and the OS is touchy about that. Some package that the OS relies on might get updated in an incompatible way as part of the installation of Leo, but the system can't know if that will happen. So it prefers not to install some Python packages. I have seen the same warning myself when trying to install or upgrade certain packages. I can't remember which ones, though. I didn't even know there was a *-break-system-packages option. *But it's probably not a good idea to use it unless you have some reason to know that it would not harm the system. Overall, a venv would be safer, or, as I generally have done, install a different Python version from the system's and use that for everything you want to do. I did not know about this option either ;-) I only applied it, since it was mentioned in the error msg as a possibly ~ dangerous ~ workaround - and - I could not get 'LeoInteg' working together with Leo, if Leo is installed in a Python virtual environment (venv). See my previous answer to Felix. - Have you been able to get 'LeoInteg' working in such a setup ? 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/17b55639-73d8-4494-bd0f-464f1e47841en%40googlegroups.com.
