| 1 |
On 24/11/2019 12:15, Benda Xu wrote: |
| 2 |
> Given the python-2 countdown deadline being 2020-01-01, a month away, |
| 3 |
> shall we get rid of python-2? |
| 4 |
|
| 5 |
|
| 6 |
> If the answer is no, to avoid holding back new versions having only |
| 7 |
> python3, such as bug 671796 for dev-python/matplotlib bump, old versions |
| 8 |
> with python_targets_python2_7 and new versions without should be |
| 9 |
> co-installable into different SLOTs. |
| 10 |
|
| 11 |
Rather than slots, perhaps a separate directory hierarchy containing |
| 12 |
only python2 + deps (/opt/python2 ?) i.e. it's just a --prefix change |
| 13 |
|
| 14 |
It's ugly I know but the advantage is the majority of installations with |
| 15 |
python3 don't see any change and they'll have a clean python3 only /usr. |
| 16 |
Anyone who wants/needs python2 will be happy to put up with the ugliness |
| 17 |
and pull all the duplicate deps in (yes, have duplicate set of ebuilds |
| 18 |
for python2 only deps - dev-python2/* - forked off and with the |
| 19 |
understanding that no new features, this is a semi-temporary situation |
| 20 |
until python2 can finally die properly). Also, I think it helps everyone |
| 21 |
psychologically to have a very visible separation. |
| 22 |
|
| 23 |
Not being a dev and with my lack of a deep understanding of python |
| 24 |
there's probably an big reason this idea is a non-starter, so just |
| 25 |
throwing it out there. |
Archives