| 1 |
On Wed, Mar 10, 2010 at 11:43:04PM +0100, Ben de Groot wrote: |
| 2 |
> On 10 March 2010 18:36, Arfrever Frehtes Taifersar Arahesis |
| 3 |
> <Arfrever@g.o> wrote: |
| 4 |
> > Almost everybody has at least 1 package installed which supports both Python 2 |
| 5 |
> > and Python 3 and depends on dev-lang/python without version specification, |
| 6 |
> > so Python 3 would be pulled into dependency graph, |
| 7 |
> |
| 8 |
> The problem is that we want to prevent that from happening. |
| 9 |
> Or at the very least advise our users that they should mask |
| 10 |
> python-3* unless they want it to be pulled in. |
| 11 |
|
| 12 |
If someone has a package that truly works with either python 2 or 3, |
| 13 |
what is the harm in automatically pulling in python 3 and installing |
| 14 |
the package for both python 2 and 3? |
| 15 |
|
| 16 |
As long as pulling in python-3 doesn't change the system's default |
| 17 |
python interpretor I don't see a problem with having them both |
| 18 |
installed. |
| 19 |
|
| 20 |
William |
Archives