I had a list of 120 items I wanted to construct for a configuration file. After
editing 20 of them I thought, this is nuts, it'll take me forever. So I decided
to write a simple python script. I took a look at a Python program I wrote many
years ago, but it was much more complex than I remebers, with making
directories, handling a fair number of command-line options, file-tree walking.
Too much, so I made a small script to do the job and it was pretty easy.

Now I want to run an audio/MIDI session manager. The JACK project ported the
Non Session Manager as the "New Session Manager", and includes the original
GUI. But I wanted something a little more modern.

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.

--
Q: How do you stop an elephant from charging?
A: Take away his credit cards.

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?

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

On Mon, 13 Jan 2025 11:27:30 -0500, Chris Ahlstrom 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.
>

You are a brave person indeed.

Whenever I encounter a project that requires Python I run away
like mad.

It could be that any developer who chooses Python is totally
incompetent.

It could be something else.

But whatever, it is no Python for me ever.

--
Systemd: solving all the problems that you never knew you had.

On Mon, 13 Jan 2025 22:03:04 +0000, Farley Flud <ff@linux.rocks> wrote in
<pan$de392$a8fd95f1$d57dc675$fcade1a8@linux.rocks>:

> On Mon, 13 Jan 2025 11:27:30 -0500, Chris Ahlstrom 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.
>>
>>
> You are a brave person indeed.
>
> Whenever I encounter a project that requires Python I run away like mad.
>
> It could be that any developer who chooses Python is totally
> incompetent.
>
> It could be something else.
>
> But whatever, it is no Python for me ever.

How can you tell when Feeb is wrong? Whenever
he writes.

(His distro's package manager uses Python.)

--
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
OS: Linux 6.13.0-rc7 Release: Mint 21.3 Mem: 258G
"I used to have a handle on life, then it broke."

On 1/13/25 5:03 PM, Farley Flud wrote:
> On Mon, 13 Jan 2025 11:27:30 -0500, Chris Ahlstrom 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.
>>
>
> You are a brave person indeed.
>
> Whenever I encounter a project that requires Python I run away
> like mad.
>
> It could be that any developer who chooses Python is totally
> incompetent.
>
> It could be something else.
>
> But whatever, it is no Python for me ever.

Python is perfectly good, so WHERE could the
problem be .... :-)

On Mon, 13 Jan 2025 20:55:45 -0500, 186282@ud0s4.net wrote:

> Python is perfectly good, so WHERE could the problem be ....

A world renown C programmer would never stoop to something as plebeian as
Python. Why do something adequate for the task in 50 lines when you can do
it in 500?

On Tue, 14 Jan 2025 04:16:49 +0000, a bunch of assholes wrote:

>
>
>> Python is perfectly good, so WHERE could the problem be ....
> [snip remainder of collective idiocy]

I do beg your fucking pardons. I should have said that I will run like
hell from Python GUI projects. Repeat: I will run like hell from Python
GUI projects.

But I assumed that it would be undestood from the context of the OP.

However, the proper understanding of context requires a modicum of
intelligence which you all fucking buzzards do not possess.

--
Hail Linux! Hail FOSS! Hail Stallman!

On 1/13/25 11:16 PM, rbowman wrote:
> On Mon, 13 Jan 2025 20:55:45 -0500, 186282@ud0s4.net wrote:
>
>> Python is perfectly good, so WHERE could the problem be ....
>
> A world renown C programmer would never stoop to something as plebeian as
> Python. Why do something adequate for the task in 50 lines when you can do
> it in 500?

Depends - do you get paid by the hour ? :-)

In any case, Python isn't THAT much more verbose, and
it's easier to understand. Yer 'C' code may be smaller,
but ideally there's a LOT of comment lines .... even
you won't understand half of it in a year or two.

But, as said, I often split the diff and program
in Pascal.