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