Hello, I played around and encounter problems with Python 3.6. The details not important. But in that context I found out that Python 3.6. is dead since December 2016 and not officially support by Python.org itself. [1] Because of that we should drop the 3.6. support. I would take care of that. Any suggestions or vetos? Kind Christian [1] -- <https://www.python.org/downloads/release/python-360/>
Hi! I'm afraid that Ubuntu LTS 18.04 is still actively supported (officially until April 2023), and ships with Python 3.6.7: https://packages.ubuntu.com/bionic-updates/python3 Also, CentOS 7 shipped with Python 2.7.x, and the latest community(?) package available is 3.6.x: https://linuxstans.com/how-to-install-python-centos/ I'm not saying that this should be our main guideline, but we should keep that in mind while we make a decision about which Python versions we want to support. Cheers, Michael On 18.09.2022 11:32, c.buhtz@posteo.jp wrote:
Hello,
I played around and encounter problems with Python 3.6. The details not important.
But in that context I found out that Python 3.6. is dead since December 2016 and not officially support by Python.org itself. [1]
Because of that we should drop the 3.6. support.
I would take care of that. Any suggestions or vetos?
Kind Christian
[1] -- <https://www.python.org/downloads/release/python-360/> _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: foss@michael-bueker.de
Moin Michael, I see and learn. It is a bit shocking. ;) I am to naive and give to much value in words like "stable" or "LTS". :D
I'm afraid that Ubuntu LTS 18.04 is still actively supported (officially until April 2023), and ships with Python 3.6.7:
Ubuntu 18 is still a "supported" LTS version. Why do they have 3 LTS branches? But it seems to me that "LTS" in Canonical products is not worthy of being called that. They ship 3.6.7 which is has known security issues which are fixed in the 3.6.18 (the last upstream release in the 3.6.* branch). IMHO this is not what I would name "support". And Ubuntu 18 is the previous before previous (how do you say that: "Die vor-vorherige Version"). It you want Ubuntu LTS you can use Ubuntu 20 (which is what TravisCI is using) or Ubuntu 22 (quit fresh). And the people say that Debian is outdated. :D We don't need to support every existing LTS version, even if it wasn't Canonical but a "better and more friendly" company behind it. Am 18.09.2022 12:58 schrieb Michael Büker:
Also, CentOS 7 shipped with Python 2.7.x, and the latest community(?)
The same arguments here.
I'm not saying that this should be our main guideline, but we should keep that in mind while we make a decision about which Python versions we want to support.
Yes I see. IMHO the point is that if distros offer LTS versions and want to support software that isn't supported by upstream anymore they have to take care of that themself. When we ship a BIT supporting Python 3.7 or higher which doesn't build/run on Python 3.6 they need to patch this themself. There LTS there responsibility. The support deadlines of upstream are more important to me. And Python has very long and friendly support timelines. I need to do some more tests with my Qt-on-Travis problem. And maybe then I can come up with a better argument why we should drop 3.6. ;) Greetings Christian
On Sun, 2022-09-18 at 09:32 +0000, c.buhtz@posteo.jp wrote:
I played around and encounter problems with Python 3.6. The details not important. ... Because of that we should drop the 3.6. support.
I'd prefer to stay as far backwards-compatible a possible until there are real hard reasons to drop the support. If it is "only" due to Travis CI (which is a beast ;-) it is possible better to skip unit tests on travis if the python version is too old (skip on travis I have seen in the unit tests, not sure if there also exists a conditional skip on travis and python version but this could be as simple as an "if")...
I'll agree with both of you: Christian is right that we shouldn't let the laziest of "LTS" distributions determine which old software we need to deal with. But on the other hand, we shouldn't drop support unless we have a good reason, like security, highly desirable deatures or significant gains in performance. Cheers :) Michael On 18.09.2022 13:25, J. A. wrote:
On Sun, 2022-09-18 at 09:32 +0000, c.buhtz@posteo.jp wrote:
I played around and encounter problems with Python 3.6. The details not important. ... Because of that we should drop the 3.6. support.
I'd prefer to stay as far backwards-compatible a possible until there are real hard reasons to drop the support.
If it is "only" due to Travis CI (which is a beast ;-) it is possible better to skip unit tests on travis if the python version is too old (skip on travis I have seen in the unit tests, not sure if there also exists a conditional skip on travis and python version but this could be as simple as an "if")...
participants (3)
-
c.buhtz＠posteo.jp -
J. A. -
Michael Büker