Re: [gentoo-python] [PATCH] Support overriding PYTHON_COMPAT.

["Nikolaj Sjujskij" <sterkrig@myopera.com>]

Den 2013-03-13 23:49:33 skrev Michał Górny <mgorny@gentoo.org>:

> On Wed, 13 Mar 2013 13:20:19 +0400
> "Nikolaj Sjujskij" <sterkrig@myopera.com> wrote:
>
>> Den 2012-12-13 14:44:41 skrev Michał Górny <mgorny@gentoo.org>:
>>
>>> PYTHON_COMPAT_OVERRIDE is an environment variable which overrides
>>> the current value of PYTHON_COMPAT.
>>>
>>> Useful for testing packages with new Python implementations quickly
>>> without modifying the ebuild. Outputs a lot of noisy warnings to make
>>> sure people notice how hacky it is.
>>>
>>> Example use:
>>>
>>> $ PYTHON_COMPAT_OVERRIDE=python3_3 emerge -1v dev-python/nose
>>
>> Has it been pushed to tree?
>>
>>   % grep -r PYTHON_COMPAT_OVERRIDE /usr/portage/eclass/*
>> <nothing>
>>
>> And I don't see anything related in ML archives. Have I missed  
>> something?
>
> It couldn't work properly, so I withdrawn it. The major problem is that
> metadata becomes affected by environmental variables.
>
> Sadly, portage can't handle that nicely. Usually, it just results in
> portage 'sticking' with one particular set of USE flags on the package
> and trying to use the other one at the same time. In other words, a lot
> of random behavior and QA warnings.
>
> Probably, the nearest thing that could work is PYTHON_COMPAT_OVERRIDE
> which doesn't use the USE flags but instead forces all impls listed.
  I see... Well, that's unfortunate, I hoped to test pylint with it,  
hacking ebuild just for changing PYTHON_COMPAT isn't much fun.