On Thu, Sep 11, 2014 at 07:18:07PM +0200, Oliver Tappe wrote: > > On 2014-09-11 at 12:28:50 [+0200], Jessica Hamilton > <jessica.l.hamilton@xxxxxxxxx> wrote: > > On 11/09/2014 6:13 PM, "pulkomandy" <pulkomandy@xxxxxxxxxxxxx> wrote: > > > > > > Hi there, > > > The WebKit team is about to start requiring Python 2.7 starting next > > > week. We still have only 2.6.9 in our repositories. Are we ready to > > > migrate to 2.7 or should we ask them to delay the switch? > > > > Shouldn't we be able to provide both versions with package management, and > > even have them both installed? > > As long as the packages have different names and provides (i.e. python26 > and python), this is possible. Of course, only one of those packages can > provide the 'python' binary (the other one would have to resort to > 'python-2.6' or similar). > > But in general I'd prefer it if we could restrain ourselves to stick to a > single version of python 2. If we decide to support two different versions > of python, it should be 2.x and 3.x. That would be nice, but there isn't even a working haikuporter recipe for Python 3, so I think migrating to 2.7 is likely to be faster. -- Adrien.