Python 3.8 transition

[paxmark1]

This will only affect those in Sparky Rolling.  It will start in few days from now for Rolling, and less problems will occur in Testing-Rolling than in Sid-Unstable

Short advice - do not do "apt autoremove" or the analogous action in aptus for a short while.  If the "apt  full-upgrade"   has multiple removals that you are not sure of, just type "n" to abort and wait - see - investigate.  Bugs do occur in Rolling-testing - especially around transitions. 

The Python 3.8 transition is starting.  After that is the Python2-rm

Code [Select]

https://release.debian.org/transitions/html/python3.8-default.html

From a Sid distro forum  in Deutsch (translation availabe)

Code [Select]

https://forum.siduction.org/index.php?topic=7896.msg64162

Example of mine in Sid - Wayland and Sway WM

Code: [Select]

apt full-upgrade -d
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  geoclue-2.0 hplip-data iio-sensor-proxy kitty-doc kitty-terminfo libdns-export1107 libdvdnav4 libdvdread7 libgdata-common libgdata22 libgoa-1.0-0b libgoa-1.0-common libisc-export1104 libjansson4
  libjs-sphinxdoc libjs-underscore libldb2 liblua5.2-0 libmm-glib0 libmtp-common libmtp-runtime libmtp9 libnfs13 libpython3.7 libpython3.7-dev libqt5positioning5 libqt5sensors5 libqt5webchannel5
  libqt5webkit5 libsane-hpaio libtalloc2 libtevent0 libva-wayland2 libwbclient0 libweston-6-0 phantomjs python3-pexpect python3-ptyprocess python3-pyxattr python3.7-dev rtmpdump youtube-dl
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

As far as the Python2-rm, complaints that program "XYZ" that is going to disappear - well the developers of program "XYZ" had 10 years to port to Python3.  I am looking forward to saying hello to Python4 in the future. 

peace out,

[paxmark1]

In the pursuit of excellence Linux and Debian do remove things that are a "piece of crap"  - and people will have to adapt or complain, hopefully the former.

Thish only affects people in Rolling-Testing.  This does not affect Stable  Sparky.

Via PlanetDebian

Code [Select]

https://www.enricozini.org/blog/2020/python/python-2-is-dead/

Code [Select]

https://mail.python.org/archives/list/python-announce-list@python.org/thread/OFCIETIXLX34X7FVK5B5WPZH22HXV342/

via Wikipedia

Python 2.0, released October 2000

Python 3.0 (also called "Python 3000" or "Py3K") was released on December 3, 2008.[9] It was designed to rectify fundamental design flaws in the language—the changes required could not be implemented while retaining full backwards compatibility with the 2.x series, which necessitated a new major version number. The guiding principle of Python 3 was: "reduce feature duplication by removing old ways of doing things".

No Python4 yet   3.9.5 Alpha is the bleeding edge available directly from Python.  And yes, most of the little add on scripts for Calibre will not work.  Pyrenamer is gone, the list goes on for packages no one ported.