| 1 |
On 11 March 2010 01:25, William Hubbs <williamh@g.o> wrote: |
| 2 |
> If someone has a package that truly works with either python 2 or 3, |
| 3 |
> what is the harm in automatically pulling in python 3 and installing |
| 4 |
> the package for both python 2 and 3? |
| 5 |
> |
| 6 |
> As long as pulling in python-3 doesn't change the system's default |
| 7 |
> python interpretor I don't see a problem with having them both |
| 8 |
> installed. |
| 9 |
|
| 10 |
I've seen enough python-3 specific bugs to know it is not without |
| 11 |
problems. It's a waste of time and resources for something that is |
| 12 |
not ready to be used anyway. While it can be argued that that is |
| 13 |
what our testing branch is for, it is certainly not something that |
| 14 |
should be pushed to stable users. |
| 15 |
|
| 16 |
Even if it would be just "dead weight", it is not something we should |
| 17 |
wish for. It is bloat, it is unnecessary, and causes more problems |
| 18 |
than that it solves. Why should users have to compile multiple |
| 19 |
python versions, if they only use one anyway? |
| 20 |
|
| 21 |
Cheers, |
| 22 |
-- |
| 23 |
Ben de Groot |
| 24 |
Gentoo Linux developer (qt, media, lxde, desktop-misc) |
| 25 |
______________________________________________________ |
Archives