| 1 |
On 02 Jun 2015 06:49, Alexander Berntsen wrote: |
| 2 |
> On 02/06/15 06:42, Mike Frysinger wrote: |
| 3 |
> > the portage ebuild dropped support: |
| 4 |
> > python 3.1: 21 months ago |
| 5 |
> > python 2.6: 10 months ago |
| 6 |
> > python 3.2: 8 weeks ago |
| 7 |
> > |
| 8 |
> > the python team itself no longer supports these versions either and |
| 9 |
> > it's not possible to install other modules using them. they're |
| 10 |
> > already forcing you to pick 2.7 or 3.3+. |
| 11 |
> You make a compelling case here. |
| 12 |
> |
| 13 |
> > plus, i'm not talking about changing existing releases, just new |
| 14 |
> > ones, which means it's going to be a while before people are |
| 15 |
> > completely impacted. |
| 16 |
> I realise that. Anything else would be stupid. |
| 17 |
> |
| 18 |
> > at some point we have to move forward and the shims for 2.6/3.1/3.2 |
| 19 |
> > are holding us back now. 2.6 is obvious enough, but 3.1 & 3.2 are a |
| 20 |
> > pain due to the unicode differences. conversely, py2.7 and py3.3+ |
| 21 |
> > have the same unicode literal format. |
| 22 |
> I agree on all points. |
| 23 |
> |
| 24 |
> |
| 25 |
> So I think this patch would be fine to merge. I'd like Brian to chime in, but I'm a tentative +1. |
| 26 |
|
| 27 |
<dol-sen> but yeah, I don't see a problem in dropping them |
| 28 |
<zmedico> yeah |
| 29 |
<dol-sen> especially since gkeys is not 3.2 capable |
| 30 |
<dol-sen> and I'm starting to integrate it in portage |
| 31 |
<zmedico> those pythons are ancient |
| 32 |
-mike |
Archives