pkgsrc-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Python 3.6 retirement

Peter Lai <> writes:

> On Sat, Oct 9, 2021 at 7:40 PM Greg Troxel <> wrote:

>> Regarding nia@'s point about Solaris 10, it would be nice for Solaris
>> people to comment on why newer python can't reasonably be made to work
>> by fixing either Python or Solaris.  Maybe this really is intractable,
>> but that would seem somewhat surprising.  Agree that the presence of 3.6
>> is not causing that much, if any, trouble, and that accomodating people
>> is nice if it doesn't hurt.
> There is a reason why we support PYTHON_VERSIONS_ACCEPTED and

If you mean that having 3.6  in tree doesn't hurt because if some
package doesn't work with 3.6 we can just mark it, agreed.  If you mean
something else, I didn't follow.

For Solaris 10, I looked in python37 to find BROKEN_ON and didn't.  So
if people care about pkgsrc on Solaris 10, it would be good for them to
address newer python.

> Note that upstream will support 3.6 until 2021-12. Perhaps target 22Q1
> release for removal to align with this.

Good to know, so that argues for not now.  After the EOL date, the
Solaris 10 issue is the only reason I'm aware of why anyone would want
to run 3.6.  Thereefore dropping 3.6 in January seems reasonable, absent
an argument from Solaris 10 people or others that there is a good reason
ii should stay.

> Upstream EOL for PY37 is 2023-06.

That's a ways out.   I hadn't realized there was a 2-year gap between
3.6 and 3.7.

>> It would be interesting to a bulk build or a few, identifying the count
>> of packages that do and don't build with 3.8.  Other than 3.8 not
>> running on some platform, I wonder how much there really are good
>> reasons to run 3.6 or 3.7 instead of 3.8, other than not having updated
>> yet.
> Mostly change control prioritization (coordination/testing/validation
> requirements) for folks in production environments that have a bunch
> of abi-dependent pkgsrc python packages (numpy, psycopg2, etc.).

Sure, but pkgsrc switched away from 3.6 as default long ago, and when
2021Q4 comes out, it will have been 2 years and 8 months.   That's IMHO
more than long enough, and of course anybody who wants longer is welcome
to use the old pkgsrc bits or do whatever.

3.7	2019-04-24
3.8	2020-12-04
3.9	2021-10-01

But, this makes me disinclined to drop 3.7 soon, as it's still in
support and has not even been default for a full year.   It does feel
like we are carrying a lot of versions, but python is releasing minor
versions every year, and it seems they take a year to get to the point
where they can be made default, a year of default, a year of old, and
year of plus-old.

Attachment: signature.asc
Description: PGP signature

Home | Main Index | Thread Index | Old Index