Date: Sat, 1 Nov 2025 16:19:35 +0100 From: Matthias Andree <mandree@FreeBSD.org> To: core <core@freebsd.org> Cc: portmgr <portmgr@FreeBSD.org>, python <python@freebsd.org> Subject: vishwin@ obstruction again - we'll lose supported Python for FreeBSD 15. Message-ID: <3c566a68-519b-4799-b071-b2896a4c759a@FreeBSD.org>
index | next in thread | raw e-mail
[resending with a valid 2nd cc: address - the first send bounced from the invalid cc:, no damage done] Greetings core@ team, in a past motion, core@ offered to work with vishwin@ to get him to not constantly obstruct ports progress, and I am seeking to take core@ up on the offer. I seek a core@ motion to forbid Python 3.13 be added unless 3.14 be added at the same time (this contradicts my public fortnight ultimatum I imposed on https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274671#c37 - which isn't nice, but read on). Please provide a timeline until we have Python 3.13 and/or 3.14 or remove vishwin@ at least from Python@'s team so we can get Python 3.13 and 3.14 working. At least one of them should be part of FreeBSD 15. He's going down rabbit holes again trying to do a past-perfect solution of everything, without sufficient time at his hands, and note Python releases minors yearly, supporting them two years for fixes. So it's one year past 3.13 release and we still don't have it for nonsense reasons, and there's less of one year 3.13 bugfix support left, adding that version with 3.14 already released does not make sense, it's only adding more workload on Python@ which are clearly overworked. -- Matthias Andree FreeBSD ports committerhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3c566a68-519b-4799-b071-b2896a4c759a>