Date: Wed, 02 Apr 2025 14:16:01 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 274671] lang/python313: New port, 3.13.2 release Message-ID: <bug-274671-21822-CTshpdmVNC@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-274671-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-274671-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D274671 --- Comment #13 from p5B2EA84B3@t-online.de --- What exactly prevents the committing of lang/python3.13 as a new port. I do see Wen's attachments but not an initial commit for creating the port. I do need to understand the criteria/policy if any for porting new Python releases.=20 We had python 3.10.0.beta4, 3.10.0rc1, 3.10.0rc2 as ports but do fail to provide actual Python releases for 3.12 and 3.12.=20 What's going on here please? What is the point of failure? I do NOT criticize Wen here, as he is doing a great job by providing port-upgrades for Python in typically less than 5 days. And he is the one providing upgrade attachments. But there is an issue for getting the first (3.x.0 versions) releases in a reasonable timely manner as a port. And yes, upgrading Python default versions looked also more like <fill in a appropriate word yourself> than anything else. But this is another story and still needs to be improved. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-274671-21822-CTshpdmVNC>