Python Does Team Python need a hand?

[Phishfry]

I can't help to notice upstream python has changed packaging and many older ports are going to need to have their packaging fixed.
Some of these programs I do not use or don't care about but I do like having a robust ports tree. Old Python programs included.

This seems like a good time to send out an SOS. Bring in some extra help for the push.
As a user I am willing to help out. How can I start?

I see that comms/py-pyserial uses distutils.
That will need to be fixed.
Do we have a starting line here? I saw some fixes in the PR for py-setuptools upgrade to 81.0
Should patches be provided per port? Is there any coordination on fixing older ports?

So any py-port that uses distutils need to be fixed. Correct? Updated to PEP517 specs.

 

[Phishfry]

py-pyserial might have been a bad example.

There is active maintainer on it.

FreeBSD Support for list_ports by kev009 · Pull Request #861 · pyserial/pyserial

Fixes over the original PR #778: Call super().init() so base ListPortInfo attributes are initialized Parse angle-bracket description properly with regex instead of split() which mangled the USB de...

github.com

Probably waiting on setuptools =>77.0.3

[build-system]
requires = ["setuptools>=77.0.3"]

I will start looking at the un-maintained py-ports.

 

[xibo]

I'm not authoritative for python, but as a former kde ports maintainer I can tell you that so far all teams of FreeBSD ports I met were happy to get additional hands. Just drop a mail to the freebsd-python mailing list explaining the problem (they might already be aware of it but it's better to explain it nevertheless), and how you intend to solve it. They might give you hints or explain you how the merge process to the python ports works.