On 02 Jun 2015 06:49, Alexander Berntsen wrote: > On 02/06/15 06:42, Mike Frysinger wrote: > > 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+. > You make a compelling case here. > > > 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. > I realise that. Anything else would be stupid. > > > 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. > I agree on all points. > > > So I think this patch would be fine to merge. I'd like Brian to chime in, but > I'm a tentative +1.
<dol-sen> but yeah, I don't see a problem in dropping them <zmedico> yeah <dol-sen> especially since gkeys is not 3.2 capable <dol-sen> and I'm starting to integrate it in portage <zmedico> those pythons are ancient -mike
signature.asc
Description: Digital signature
