Discussion:
Bug#1084600: mono: removal of Python standard libraries in Python 3.13
(too old to reply)
Antoine Le Gonidec
2024-10-07 16:40:01 UTC
Permalink
Thank you for the heads up!

As I only very recently took over the maintenance of src:mono, that has
been before that unmaintained for many years, I still have little
konwledge of its codebase and build chain.

My first step is going to check if I can simply drop this vendored
boringssl source (with a bit of luck it is not required for anything
really important).

If I can not do that I might have to find a way to patch it to drop the
requirement on the deprecated "pipes" library. If it comes to that,
could I expect some help (or at least advice) from the Python team?

PS: Please keep ***@bugs.debian.org in the loop, as I am not
subscribed to the Python list (yet).
Colin Watson
2024-10-08 15:00:01 UTC
Permalink
Post by Antoine Le Gonidec
My first step is going to check if I can simply drop this vendored
boringssl source (with a bit of luck it is not required for anything
really important).
If I can not do that I might have to find a way to patch it to drop the
requirement on the deprecated "pipes" library. If it comes to that,
could I expect some help (or at least advice) from the Python team?
In this case the fix is straightforward. Nowadays you can safely assume
Python 3.3 or newer, and therefore you can replace "import pipes" with
"import shlex" and "pipes.quote" with "shlex.quote"; that seems to be
all that this script needs.
--
Colin Watson (he/him) [***@debian.org]
Antoine Le Gonidec
2024-10-08 17:10:01 UTC
Permalink
Post by Colin Watson
In this case the fix is straightforward. Nowadays you can safely
assume Python 3.3 or newer, and therefore you can replace "import
pipes" with "import shlex" and "pipes.quote" with "shlex.quote"; that
seems to be all that this script needs.
Thanks for the easy fix suggestion, if I can not simply remove the
shipped boringssl source I’m going to add a patch applying the changes
you suggest.

Loading...