[arch-dev-public] Killing Python 2 (v2)
Hi All, 2020 happened and Python 2 is very much still alive, even worse there will be an update in April. However we should actively strive to get rid of Python 2 before it. Some upstreams are (still) working on porting to Python 3 such as Kodi, inkscape, mercurial and many more but for packages with dead upstreams and being unrequired I propose we remove them. For packages still providing python2 functionality such as vim and others I propose we remove python2 support to actively to discourage people using it. Dropping non-ported python2 packages: * rox - python2, dead and GTK2 * wifite - upstream dead * shedskin - python2 specific, won't be updated * jmc - dead upstream * pydb - python debugger (python2 specific) * pyrex - dead upstream * mcomix - dead upstream * singularity - dead upstream * pathological - dead upstream * armagetronad - dead upstream, optional dep can be removed * ming - no python2 compatibility * ipcheck - dead upstream * mediaproxy - dead upstream * wicd/wicd-gtk - dead upstream, better alternatives available * sgmltools-lite - dead upstream # Remove python2 support * pycharm-community-edition - remove python2 support * vim - remove python2 support * graphviz - remove python2 bindings or update to python3 * notmuch - switch to python3 bindings * libproxy - remove python2 bindings * many others! Greetings, Jelle van der Waa
On Thu, Jan 02, 2020 at 05:12:33PM +0100, Jelle van der Waa wrote:
For packages still providing python2 functionality such as vim and others I propose we remove python2 support to actively to discourage people using it.
I was +1 on this
# Remove python2 support
* pycharm-community-edition - remove python2 support * vim - remove python2 support
Until I saw this. I imagine editors and such may/could be an exception? Cheers! -Santiago
On 01/02/20 at 11:18am, Santiago Torres-Arias via arch-dev-public wrote:
On Thu, Jan 02, 2020 at 05:12:33PM +0100, Jelle van der Waa wrote:
For packages still providing python2 functionality such as vim and others I propose we remove python2 support to actively to discourage people using it.
I was +1 on this
# Remove python2 support
* pycharm-community-edition - remove python2 support * vim - remove python2 support
Until I saw this.
I imagine editors and such may/could be an exception?
So following up from what grazollini and Eli have said, I guess we can keep it for vim, maybe focus more on optdepends and actual makedepends for I've found a lot of gnome packages having a python2 makedepends which can be removed or moved to python 3. Felix brought up a more radical approach of removing check() for python2 modules which would allow a lot of python2 modules to be removed. This is also blocking him from updating packages since he needs to bring new python2 modules in to update some python/python2 modules iirc. Felix, can you enlighten us? I don't want you to be blocked from keeping Arch rolling =) Greetings, Jelle van der Waa
On 1/2/20 11:12 AM, Jelle van der Waa wrote:
# Remove python2 support
* pycharm-community-edition - remove python2 support
Seems reasonable to not encourage people to use python2 in an IDE these days.
* vim - remove python2 support
Are there any stats on vim ecosystem plugins which use the python2 binding? Including non-packaged plugins? Because it's more annoying to disable support for python2 in something that requires recompiling the package to use it, and if we have packaged plugins which use python2 then we definitely cannot remove non-leaf functionality first. Most other things like bindings could most likely be built separately if someone really needed them...
* graphviz - remove python2 bindings or update to python3 * notmuch - switch to python3 bindings * libproxy - remove python2 bindings
These all seem perfectly reasonable, no different from dropping any python2 leaf module that serves no useful purpose.
* many others!
Greetings,
Jelle van der Waa
-- Eli Schwartz Bug Wrangler and Trusted User
Em janeiro 2, 2020 13:24 Eli Schwartz via arch-dev-public escreveu:
* pycharm-community-edition - remove python2 support
Seems reasonable to not encourage people to use python2 in an IDE these days.
Hi All, As we have discussed on IRC, I think that editors and python2 *lint* and *syntax* checkers, should be exempt from this. I'm for one use pycharm *a lot* and I'm expected/expecting to convert thousands of python2 code to python3 code in the coming *years*, not months, years. I'm perfectly fine installing python2 from the AUR for *running* python2 code, but how can people be encouraged to convert python2 code without even being able to syntax check it? So, in that regards, editores/linters/syntax checkers/etc, should be exempt from this, but *only* if they don't necessarily require python2 for that. As far as I know, pycharm doesn't require python2 itself for syntax highlighting and lint. Don't know about the others though. Regards, Giancarlo Razzolini
On 2/01/2020 17:24, Eli Schwartz via arch-dev-public wrote:
On 1/2/20 11:12 AM, Jelle van der Waa wrote:
# Remove python2 support
* pycharm-community-edition - remove python2 support
Seems reasonable to not encourage people to use python2 in an IDE these days.
* vim - remove python2 support
Are there any stats on vim ecosystem plugins which use the python2 binding? Including non-packaged plugins?
You can safely remove python2 support from vim. The python2 support is only needed for vim plugins using python2, python2 can be perfectly linted by vim without python2-plugin support. *Most* plugins got forced to support both python2 and 3 when ubuntu default vim came without python2. So it should be fine and you can still install python2 from AUR or whatever to do the proper linting.
On 1/2/20, Jelle van der Waa <jelle@vdwaa.nl> wrote:
* armagetronad - dead upstream, optional dep can be removed
Fixed instead. It still works a treat. -Kyle
On 01/02/20 at 07:09pm, keenerd via arch-dev-public wrote:
On 1/2/20, Jelle van der Waa <jelle@vdwaa.nl> wrote:
* armagetronad - dead upstream, optional dep can be removed
Fixed instead. It still works a treat.
Thanks a lot! This was my hidden agenda all along ^_^ I've found many packages which have been building with Python 3 but simply weren't adjusted yet Thanks in advance, Jelle van der Waa
On 1/2/20, Jelle van der Waa <jelle@vdwaa.nl> wrote:
* rox - python2, dead and GTK2
Also was an easy fix. Well, the python2 part at least. -Kyle
On 1/2/20 7:19 PM, keenerd via arch-dev-public wrote:
On 1/2/20, Jelle van der Waa <jelle@vdwaa.nl> wrote:
* rox - python2, dead and GTK2
Also was an easy fix. Well, the python2 part at least.
-Kyle
https://bugs.archlinux.org/task/65023 There are a couple of forks apparently, which might be worth looking into and/or asking about gtk3: https://sourceforge.net/p/rox/mailman/rox-users/thread/159e19f9-3379-c689-10... https://github.com/jun7/rox-filer -- Eli Schwartz Bug Wrangler and Trusted User
Le jeu. 2 janv. 2020 à 17:12, Jelle van der Waa <jelle@vdwaa.nl> a écrit :
Hi All,
2020 happened and Python 2 is very much still alive, even worse there will be an update in April.
However we should actively strive to get rid of Python 2 before it. Some upstreams are (still) working on porting to Python 3 such as Kodi, inkscape, mercurial and many more but for packages with dead upstreams and being unrequired I propose we remove them.
For packages still providing python2 functionality such as vim and others I propose we remove python2 support to actively to discourage people using it.
Texlive packages contain random Python scripts, a few of them might be ported to Python 3. As far as I know none of them is critical, I will simply remove the shebang rewriting in next packages and drop python2 from optdepends. I'll try to have a closer look to the ones accessible from PATH and actively remove them from /usr/bin if they are not ported. Rémy
There's getmail missing in this list. There's no python v3 port or serious work happening. Whenever we drop python v2 we will drop getmail as well. In generell I'm not for keeping python v2 support any longer. I'm for announcing a public deadline and then drop everything that will not be ported. -Andy
On 01/02/20 at 05:12pm, Jelle van der Waa wrote:
Hi All,
2020 happened and Python 2 is very much still alive, even worse there will be an update in April.
Looking at unneeded orphans on archweb we can remove more packages if no one adopts them at the end of the week: [1] * mypaint * oblogout * ocrfeeder [1] https://www.archlinux.org/devel/reports/unneeded-orphans/ P.S. seems it's time for a new year cleanup! -- Jelle van der Waa
participants (8)
-
Andreas Radke
-
Eli Schwartz
-
Giancarlo Razzolini
-
Ike Devolder
-
Jelle van der Waa
-
keenerd
-
Rémy Oudompheng
-
Santiago Torres-Arias