Re: pg_upgrade Python version issue on openSUSE

From: "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: pg_upgrade Python version issue on openSUSE
Date: 2020-10-03 09:04:10
Message-ID: 20201003090410.GB18543@hjp.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2020-09-26 17:54:31 +0200, Paul Förster wrote:
> Hi Adrian,
> > On 26. Sep, 2020, at 17:43, Adrian Klaver
> > <adrian(dot)klaver(at)aklaver(dot)com> wrote:
> >
> > I suppose getting them to install Python 2 is out of the question?
> > It is an official package.
>
> I can try, but chances are at 99% that they refuse.
>
> > Well there is always going to be versioning. If you mean the
> > incompatibility split, then for 2/3 that is not going away. There
> > will be a Python 4, but the core developers have said they learned
> > their lesson and it will just be an incremental upgrade.
>
> so you're saying there will always be two Pythons? One Python 2 and
> one Python x (with x>=3)? Oh my god... Why don't they just make Python
> 3 backward compatible?

Python 2 is officially unsupported by the Python team since January 1st
2020. There has been one final release after that, but that contained
only bug fixes which were already pending before that date.

So as far as the Python team is concerned, there is only one Python and
that is Python 3.

But there is still a lot of legacy software out there and there are OSs
with very long (like 10 years) maintenance periods. So in practical
terms, Python 2 isn't dead, it just smells funny.

hp

--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp(at)hjp(dot)at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter J. Holzer 2020-10-03 11:30:50 Re: Restoring a database problem
Previous Message Paul Förster 2020-10-03 08:21:40 Re: UUID generation problem