From: "Nikolaj Sjujskij" <sterkrig@myopera.com>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-python@lists.gentoo.org, python@gentoo.org
Subject: Re: [gentoo-python] [PATCH python-r1 2/2] Introduce PYTHON_COMPAT_OVERRIDE to make testing easier.
Date: Thu, 21 Mar 2013 10:59:49 +0400 [thread overview]
Message-ID: <op.wuaa1zvgh7emz2@verkdatorn.npdb> (raw)
In-Reply-To: <20130320200343.5cebd4b0@pomiocik.lan>
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 :)
next prev parent reply other threads:[~2013-03-21 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 22:33 [gentoo-python] [PATCH python-r1 2/2] Introduce PYTHON_COMPAT_OVERRIDE to make testing easier Michał Górny
2013-03-17 23:37 ` [gentoo-python] " Mike Gilbert
2013-03-20 11:10 ` [gentoo-python] " Nikolaj Sjujskij
2013-03-20 19:03 ` Michał Górny
2013-03-21 6:59 ` Nikolaj Sjujskij [this message]
2013-03-21 10:27 ` Michał Górny
2013-03-21 11:30 ` Nikolaj Sjujskij
2013-03-21 11:55 ` Michał Górny
2013-03-21 12:12 ` Nikolaj Sjujskij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.wuaa1zvgh7emz2@verkdatorn.npdb \
--to=sterkrig@myopera.com \
--cc=gentoo-python@lists.gentoo.org \
--cc=mgorny@gentoo.org \
--cc=python@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox