| 1 |
> Seems to me that the easiest way to manage this would be to set |
| 2 |
> USE="python2" for portage in the profile, IFF you want to prevent |
| 3 |
> python:3 in the stages. |
| 4 |
> |
| 5 |
> That said, I don't see what the real issue is here. Those that want |
| 6 |
> python:2 and/or python:3 will set USE_PYTHON correctly. I am concerned |
| 7 |
> here that a vocal minority will cause some invasive change that the |
| 8 |
> silent majority cares little about. Some may find the current status |
| 9 |
> annoying, others will find the change annoying (me being one of the |
| 10 |
> latter). |
| 11 |
> |
| 12 |
> Unless someone can provide empirical data to backup any claim, one way |
| 13 |
> or the other, I would strongly suggest that no change be made, |
| 14 |
> especially without further consultation regarding the _proposed_ |
| 15 |
> change with the developer and user communities. |
| 16 |
> |
| 17 |
> Thank you for your consideration. |
| 18 |
I as a user could only +1. I can't see the issue, honestly. Those who |
| 19 |
don't like Python 3, could jolly well mask it and tweak USE_PYTHON / |
| 20 |
PYTHON_TARGETS vars. Using this ugly debianish `python3-3.2` or whatever |
| 21 |
is a step back in my opinion. Quite a lot of users could kepp their |
| 22 |
systems Python2-less. About half of Python modules (at least) work with |
| 23 |
both Python 2 and 3. Heck, even Qt3 and Qt4 were one slotted package! |
Archives