From: "Michał Górny" <mgorny@gentoo.org>
To: Mike Gilbert <floppym@gentoo.org>
Cc: gentoo-python <gentoo-python@lists.gentoo.org>
Subject: Re: [gentoo-python] RFC: Redesign for 'best implementation' in python-r1
Date: Sat, 3 Jan 2015 00:21:44 +0100 [thread overview]
Message-ID: <20150103002144.4939ecf7@pomiot.lan> (raw)
In-Reply-To: <CAJ0EP43iDwkjV4U1TXETRdTb4GveSF7r45K1520jZCk4VbzddQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
Dnia 2014-12-31, o godz. 11:41:45
Mike Gilbert <floppym@gentoo.org> napisał(a):
> >
> > As for the choice within the list the algo needs to stay as-is for now.
> > However, in the future we could either:
> >
> > a. respect EPYTHON and fallback to the other algo,
> >
> > b. respect pre-defined order i.e. 3.4 > 2.7,
> >
> > c. respect the order in PYTHON_COMPAT -- however that could be a little
> > surprising to devs.
> >
> >
> > What are your thoughts?
>
> Starting/ending with EPYTHON from the environment seems wrong, and
> doesn't seem to add value anyway.
>
> I would prefer to stick with a predefined order unless someone can
> present a case where the ebuild author really needs to control it.
Well, it isn't really about the ebuild author but about the user.
EPYTHON idea is pretty much a reference to the python-any-r1 behavior.
IOW, having both eclasses use the same preference handling.
--
Best regards,
Michał Górny
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
next prev parent reply other threads:[~2015-01-02 23:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 13:50 [gentoo-python] RFC: Redesign for 'best implementation' in python-r1 Michał Górny
2014-12-28 12:00 ` Michał Górny
2014-12-31 16:41 ` Mike Gilbert
2015-01-02 23:21 ` Michał Górny [this message]
2015-01-02 23:37 ` Michał Górny
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=20150103002144.4939ecf7@pomiot.lan \
--to=mgorny@gentoo.org \
--cc=floppym@gentoo.org \
--cc=gentoo-python@lists.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