Re: Python meanderings

In comp.os.linux.misc Chris Ahlstrom <OFeem1987@teleworm.us> wrote:

Downloaded, built, and installed the Python app "agordejo". It does not run on
this Debian system. "This application failed to start because no Qt platform
plugin could be initialized." Haven't figured that out.
 
So there's another Python-based session manager, RaySession, which is part of
the Debian repo. I install that and run it, and I get a traceback about 15
levels deep. "No module named cgitb".
 
   https://docs.python.org/3/library/cgitb.html
 
   This module is no longer part of the Python standard library. It was
   removed in Python 3.13 after being deprecated in Python 3.11. The removal
   was decided in PEP 594.
 
   A fork of the module on PyPI can now be used instead: legacy-cgi. This is a
   copy of the cgi module, no longer maintained or supported by the core
   Python team.
 
   The last version of Python that provided the cgitb module was Python 3.12.
 
Installing legacy-cgi from the link didn't work (wants a virtual setup).
But python3-legacy-cgi in the repo works, and I can now run RaySession.

If I'm looking for a program and find a Python script that does
exactly what I want, I keep looking. Too much time wasted trying to
make them run for me, or wasted later when they break compatibility
in a newer Python release.

But I have assumed that Python scripts with Debian (stable)
packages are safe because it's someone else's problem to deal with
making them run with the Python that's pacakged there. But you say
that RaySession came from "the Debian repo" so I guess that
package's maintainer couldn't even get it right. Maybe I should be
even more strict with exterminating these pesky snakes?

--
__          __
#_ < |\| |< _#