On 01 Jun 2015 23:16, Alexander Berntsen wrote: > On 30/05/15 16:58, Mike Frysinger wrote: > > We no longer support these in the ebuild and don't want to waste > > time implementing compatibility shims for them. > > In principle I don't mind this at all. > > However, should we do some sort of survey? Maybe a forum poll or > something to see if someone desperately needs them?
the portage ebuild dropped support: python 3.1: 21 months ago python 2.6: 10 months ago python 3.2: 8 weeks ago the python team itself no longer supports these versions either and it's not possible to install other modules using them. they're already forcing you to pick 2.7 or 3.3+. plus, i'm not talking about changing existing releases, just new ones, which means it's going to be a while before people are completely impacted. at some point we have to move forward and the shims for 2.6/3.1/3.2 are holding us back now. 2.6 is obvious enough, but 3.1 & 3.2 are a pain due to the unicode differences. conversely, py2.7 and py3.3+ have the same unicode literal format. -mike
signature.asc
Description: Digital signature
