[Python-Dev] Computed Goto dispatch for Python 2
ncoghlan at gmail.com
Fri May 29 09:24:32 CEST 2015
On 29 May 2015 11:01 am, "Victor Stinner" <victor.stinner at gmail.com> wrote:
> Why not continue to enhance Python 3 instead of wasting our time with
> Python 2? We have limited resources in term of developers to maintain
> (I'm not talking about fixing *bugs* in Python 2 which is fine with me.)
I'm actually OK with volunteers deciding that even fixing bugs in 2.7 isn't
inherently rewarding enough for them to be willing to do it for free on
their own time.
Stepping up to extrinsically reward activities that are beneficial for
customers but aren't intrinsically interesting enough for people to be
willing to do for free is one of the key reasons commercial open source
redistributors get paid.
That more explicitly commercial presence is a dynamic we haven't
historically had to deal with in core development, so there are going to be
some growing pains as we find an arrangement that everyone is comfortable
with (or is at least willing to tolerate, but I'm optimistic we can do
better than that).
> By the way, I just wrote sixer, a new tool to generate patches to port
> OpenStack to Python 3 :-)
> It's based on regex, so it's less reliable than 2to3, 2to6 or
> modernize, but it's just enough for my specific use case. On
> OpenStack, it's not possible to send one giant patch "hello, this is
> python 3". Code is modified by small and incremental changes.
> Come on in the Python 3 world and... always look on the bright side of
> life ( https://www.youtube.com/watch?v=VOAtCOsNuVM )!
> Python-Dev mailing list
> Python-Dev at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev