You referring to needing to use *--break-system-packages*, is that right? I don't see this as a Leo issue. 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. On Thursday, December 28, 2023 at 4:01:20 PM UTC-5 [email protected] wrote: Hello Felix, hello Edward, [snip] Shall I create a LeoInteg - or - Leo issue for it ? 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/a5629465-8c1f-46da-8cca-0a2db74770bdn%40googlegroups.com.
