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. Naturally I try to install Leo and GF4 on those distros. So I have exposure to a wider potential range of problems than most people.
Unfortunately for wrangling these issues you really need to set up new VMs each time since once you get, say, Leo working then updating is usually easier. It can all be very time consuming. On Friday, December 29, 2023 at 8:26:39 AM UTC-5 Thomas Passin wrote: > On Friday, December 29, 2023 at 6:37:55 AM UTC-5 Edward K. Ream wrote: > > On Fri, Dec 29, 2023 at 3:44 AM Viktor Ransmayr <viktor....@gmail.com> > wrote: > > > 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? > > > Big sigh. Another example of a Python "improvement" breaking existing code > or practices. > > Thomas, is this a documentation issue for Leo, or must setup.py change? > > > I don't know; I'll have to think about it some more. I just encountered > these new messages from pip in the last week or so, not in connection with > leoInteg but when trying to update Leo on one or another Linux VMs. I > assumed it was a special modification by the Distro packagers and didn't > realize it was the result of a new PEP. > > For LeoInteg one can point it to any Python executable you want, so the > answer would be to install another parallel version of Python and use > that. This would in fact also apply to Leo updates outside of LeoInteg. > But installing another Python version that's not supplied by the distro's > packager is going to be a problem for many users, and sometimes doesn't go > smoothly. Even after you get another Python version installed, whether Leo > will install and work varies across distros. Some of them require you to > install some requirement using the distro's package manager. Some of them > don't supply a certain shared library (.so file) and you have to track down > which one it is and how to install it. It's a mess. I bump up against > similar problems with my GF4 package, usually in connection with tkinter or > matplotlib. > > I suppose we should do something but I can't see what it would be that > would work across all distros. > -- 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/b09ee4a6-4d57-4cc4-b79d-c0034585dca3n%40googlegroups.com.
