From: Patrick McLean <chutzpah@gentoo.org>
To: Mike Gilbert <floppym@gentoo.org>
Cc: "Dirkjan Ochtman" <djc@gentoo.org>,
"Michał Górny" <mgorny@gentoo.org>,
gentoo-python <gentoo-python@lists.gentoo.org>
Subject: Re: [gentoo-python] unmasking python-3.3
Date: Tue, 30 Apr 2013 11:16:49 -0700 [thread overview]
Message-ID: <51800A91.1070602@gentoo.org> (raw)
In-Reply-To: <CAJ0EP40VVyHPO0HmrULgjdxHTw9bzqzez7WF_VPwbSPK-+Gh3w@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 30/04/13 08:25 AM, Mike Gilbert wrote:
> On Tue, Apr 30, 2013 at 6:34 AM, Dirkjan Ochtman <djc@gentoo.org> wrote:
>> On Tue, Apr 30, 2013 at 5:39 AM, Michał Górny <mgorny@gentoo.org> wrote:
>>>> Arfrever brought up a good point: we should adjust the default value of PYTHON_TARGETS as specified in the base profile. I think we will
>>>> need to include both python3_2 and python3_3 until dev-lang/python-3.3 has been stabilized on relevant archs.
>>>
>>> We shouldn't have two versions of Python 3 enabled by default. This will result in packages supporting only one of them to push REQUIRED_USE
>>> on users.
>>
>> Yeah, holding off on adding python3_3 to the default TARGETS until it's been stabilized (and then replacing 3.2 so we keep having only one 3.x
>> in there) seems better.
>>
>
> Alright. I'm sure there will be some whining about "sane defaults" from somebody either way we go.
>
> I guess it makes more sense to set defaults based on what is available to the stable tree.
>
Yes, I think we should definitely add it to ~arch, but not to the default PYTHON_TARGETS, USE_PYTHON until they are ready to go stable.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJRgAqRAAoJEHy/RO9cNQiD4w4QAKbj5KhI7cLZ1Ey1xYVNjkMQ
cZKSj4QUl4K42UrlR8n3E6pSsYtBDnudRsYbQoi7OEtn+oeba1Zo61UkbXS0nbj3
FrxD6d4MKs/Ndy/8iNU/qRkeXofE25/sLmQKgTDbbwPGzbXeb75ONEO+0V/jBEKM
D7zTFuVDXczdVERBxkfVtqSCIsQ+HXK+ywSwfBngYYezKqPyauRYsKXF0BUeycWn
zQ1hf8zwmcDeaLZnZVSC7sAzMw1KuZz9E05/2NwWcMCPFu9I2kg2d5CGjTbrzFhB
pZtslfXrsibxHdcI/YV6vLvPBZXnZxyWoeUj+Nwur/NOwdcDOoFpCfFQ2ykA+lAg
0jJRAnZaaxbet0un8fHw9/+PL+BRZFPpy/GWWYx8LWJGrOx3FrsYzmNlCw0tTrIY
pEnmJeLagce5TqOWdCWkizpFcaGgbF3lh2LGwULGw6JEyFP4+CtjfEhdXSWFCOY4
tvmsKt/NMpoaNNSEjX5eVM/R0QnDcjnhT9MLdYYKBuI7hoB75rugOa6/NbtMAuJi
NvQIn8DHcHZDuNmn4pHnZ2lP+QaMbu1y1G/aXkDQLBB5k9b+avv14qSP2qpLjS1h
eQVnQ+HI3qGtNaRCXXabEU5IM7lFSLgCSwUrk5snI/jUqXBdrJTIUM1Bz/QK7dNh
kDKO2dLEFBztnGdzuCQf
=+hx6
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-04-30 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 18:53 [gentoo-python] unmasking python-3.3 Patrick McLean
2013-04-29 20:47 ` Dirkjan Ochtman
2013-04-30 1:27 ` Mike Gilbert
2013-04-30 3:39 ` Michał Górny
2013-04-30 10:34 ` Dirkjan Ochtman
2013-04-30 15:25 ` Mike Gilbert
2013-04-30 18:16 ` Patrick McLean [this message]
2013-04-29 20:58 ` 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=51800A91.1070602@gentoo.org \
--to=chutzpah@gentoo.org \
--cc=djc@gentoo.org \
--cc=floppym@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=mgorny@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