There's no "blame" here, just a need to work around how the Linux packagers have decided to work. I *think* they want to split up and locate python components in particular ways to suit their packaging philosophies, so they have to modify pip, etc., to work that way.
It is possible to install Python on Linux using Linux installers /tarballs from python.org. These do come with (I think) pip and tk, but they won't be managed by the Linux update system, which utility, etc., and they may not install into the locations favored by the distro people. On Wednesday, December 28, 2022 at 1:30:10 PM UTC-5 [email protected] wrote: > Hello Thomas, > > Thanks for this explanation / info. > > [email protected] schrieb am Mittwoch, 28. Dezember 2022 um 16:16:37 > UTC+1: > >> You have to install it using the package manager. Here is what I have >> found (quoted from the Users' Guide for my GF4 project):: >> >> "On Debian/Ubuntu, tkinter has to be installed by >> the package manager: >> >> sudo apt-get install python3-tk >> > > I also double-checked & saw that 'setup.py' has added "tk" as an install > requirement. > > As I initially only did a 'git pull' on Leo's devel branch - and - did NOT > perform a subsequent 'pip install --editable > /home/user/PyVE/GitHub/Leo/leo-editor' I re-tried running the unit tests > afterwards & the same failure occurred ... > > Who is to 'blame' for treating Linux as a second-class citizen? > > Leo's 'setup.py' script - or - the Python Packagers of Debian & Fedora > Linux ... > > 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/89f59e2f-a110-4115-a133-4a80222a647an%40googlegroups.com.
