Re: Python 2 retirement — what should Guix do?

[Pjotr Prins <pjotr.public12@thebird.nl>]

The move from Python2 to Python3 will go into the history books as one
hugely mismanaged transition - call it a first order screw up. The
cost to the community is enormous, if I go by the hours I personally
already spent on managing the issue! And that just for the sake of a
few (minor) syntax changes and a new API for C extensions.

Not even the Ruby guys fucked up so badly with the transition to 2.0!
And that was bad enough. Especially the change in behaviour of Proc.

Guix is actually one of the best tools to manage the transition. I
love it for that. I don't think we should keep supporting both Python
2 and 3 versions of modules by default when the time comes. People
will do that when they need to.  I will. But we can certainly ease the
transition at little cost (to us).

So, Leo, +1 from me.

Pj.