Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On Wed, Mar 10, 2010 at 11:43:04PM +0100, Ben de Groot wrote:
> On 10 March 2010 18:36, Arfrever Frehtes Taifersar Arahesis
> <Arfrever@g.o> wrote:
> > Almost everybody has at least 1 package installed which supports both Python 2
> > and Python 3 and depends on dev-lang/python without version specification,
> > so Python 3 would be pulled into dependency graph,
>
> The problem is that we want to prevent that from happening.
> Or at the very least advise our users that they should mask
> python-3* unless they want it to be pulled in.
If someone has a package that truly works with either python 2 or 3,
what is the harm in automatically pulling in python 3 and installing
the package for both python 2 and 3?
As long as pulling in python-3 doesn't change the system's default
python interpretor I don't see a problem with having them both
installed.
William
|
|
