Date: Fri, 07 Mar 2025 16:15:19 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 271673] lang/python312: New port, update to 3.12.8 Message-ID: <bug-271673-21822-OuPNuaqcfG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-271673-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-271673-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=3D271673 j.david.lists@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |j.david.lists@gmail.com --- Comment #54 from j.david.lists@gmail.com --- Some other languages, notably gcc, have some more volatile versions that ca= n't be fully supported labelled -devel in the ports tree. E.g., lang/gcc14 vs. lang/gcc14-devel. Maybe it would be worthwhile to add newer versions of Python to the tree as lang/python312-devel or (to be *extremely* clear) lang/python312-unsupporte= d to indicate that they aren't a part of the full ports Uses/versioning scheme y= et. This would give a substantive leg up to users who only need the newer versi= ons to bootstrap a venv. As a test, I tried setting "DEFAULT_VERSIONS+=3D python=3D3.45 python3=3D3.= 45" and I got an error immediately. It looks like the same would happen for a suffixed version; the Makefile won't find it. If that existing error isn't satisfactory, it seems like it would be possib= le to get Mk/Uses/python.mk to validate the version chosen and kick out a "ple= ase meditate on the meaning of the word 'unsupported'" message if a port tries = to USES=3D or a builder tries to DEFAULT_VERSIONS=3D an unsupported version. It already has similar warnings about Python 2.7. Could even reiterate that with appropriately dire warnings in the pkg-messa= ge for unsupported versions. It may not be possible to get it to the point that no one will ever try "DEFAULT_VERSIONS+=3D python3=3D3.12-unsupported" in their make.conf and th= en complain that it's not supported. People are going to people. But hopefully= it would be more of an occasional amusement and less of an ongoing hassle. And= it might well happen less often than "How come Python 3.12 has been out this l= ong and FreeBSD doesn't have it yet?" --=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-271673-21822-OuPNuaqcfG>