Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 01 Apr 2025 14:16:24 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 285830] lang/python*: Python regards FreeBSD as Tier3
Message-ID:  <bug-285830-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285830

            Bug ID: 285830
           Summary: lang/python*: Python regards FreeBSD as Tier3
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
               URL: https://peps.python.org/pep-0011/#tier-3
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: p5B2EA84B3@t-online.de

Quote:
Tier 3 requirements would be *very weak*:

    No buildbot requirement
    No assigned core dev needed
    Don't revert a change breaking a Tier 3 platform
    Don't hold a Python release if a Tier 3 platform is broken

Currently, the "All other platforms" section is quite clear: code can
be removed anytime:

"Code changes to platforms not listed in the above tiers may rejected
or removed from the code base *without a deprecation process* if they
cause a maintenance burden or obstruct general improvements."

The only difference between "Tier 3" and "All other platforms" would
be that removing a platform from Tier 3 require a process. I'm not
sure if a deprecation is needed. But we have to go through a
discussion and someone (SC?) has to decide if it's ok to drop it
(remove code).

Removing code from Python means in practice that the support *can*
still continue, but outside of the Git upstream repository: in a fork
instead.

For me the main threat of (adding a platform to) Tier 3 is the risk
that we might never ever able to drop support for these platforms. PEP
11 would be used by users as a holy document. Maybe we should be clear
that Tier 3 is not a strong warranty of long term support, but is just
a weak status. For example, put a time bomb: if no developer was
available in the last 12 month to fix regressions, drop the platform
for Tier 3.

--

I'm thinking at these platforms for Tier 3:

    AIX 6.4 and newer (has a buildbot)
    Android API 24
    FreeBSD
    OpenBSD
    NetBSD
    s390x arch
    Solaris (has a buildbot)

I would prefer to put FreeBSD and s390x in Tier 3 rather than Tier 2.

Users of these platforms and contributors who added support for these
platforms are going to be grumpy if we drop such platform without any
warning or process.
/Quote

What needs to be done that FreeBSD gets a better Python rating?
Is there ANY effort to improve the FreeBSD-Python relations?

--=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-285830-7788>