Re: [gentoo-python] [PATCH python-r1 2/2] Introduce PYTHON_COMPAT_OVERRIDE to make testing easier.

["Michał Górny" <mgorny@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]

On Thu, 21 Mar 2013 10:59:49 +0400
"Nikolaj Sjujskij" <sterkrig@myopera.com> wrote:

> Den 2013-03-20 23:03:43 skrev Michał Górny <mgorny@gentoo.org>:
> 
> > On Wed, 20 Mar 2013 15:10:18 +0400
> > "Nikolaj Sjujskij" <sterkrig@myopera.com> wrote:
> >
> >> Den 2013-03-18 02:33:50 skrev Michał Górny <mgorny@gentoo.org>:
> >>
> >> > The PYTHON_COMPAT_OVERRIDE can be set in the environment to enforce
> >> > a different set of Python implementations than one being intersection
> >> > of PYTHON_COMPAT and PYTHON_TARGETS.
> >> >
> >> > Due to technical limitations, the variable influences only the list
> >> > of implementations actually used. USE flags, dependencies and other
> >> > metadata variables are not modified.
> >> Push it to tree, please, I'd like to test it :)
> >
> > Pushed :).
>   Yup, works fine: https://bugs.gentoo.org/show_bug.cgi?id=462566
> One minor thing. I have PYTHON_TARGETS="python2_7 python3_3" in make.conf,  
> pylint ebuild has PYTHON_COMPAT=( python2_{5,6,7} python{3_1,3_2} ). I  
> expected `PYTHON_COMPAT_OVERRIDE="python3_3" emerge -1 pylint` to install  
> pylint for both 2.7 and 3.3. Of course, it's "OVERRIDE", not "UPDATE", but  
> still.
>   A minor thing, really, and I won't insist on changing this behaviour.
> Thanks in any case :)

I've decided to go this way since you can't change the IUSE. Therefore,
you can't really control the enabled implementations via USE flags. If
it worked like you suggested, some of the implementations would respect
USE flags and some other wouldn't -- that would be confusing.

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 966 bytes --]