public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Nikolaj Sjujskij" <sterkrig@myopera.com>
To: "Krzysztof Pawlik" <nelchael@gentoo.org>
Cc: gentoo-python@lists.gentoo.org
Subject: Re: [gentoo-python] New eclass for Python
Date: Sun, 13 May 2012 10:55:57 +0400	[thread overview]
Message-ID: <op.wd7i83rph7emz2@gentoobook.trollsnaetverk> (raw)
In-Reply-To: <4FAE35B4.8010601@gentoo.org>

Den 2012-05-12 14:04:36 skrev Krzysztof Pawlik <nelchael@gentoo.org>:

>>>  - uses PYTHON_TARGETS use-expand (no more python-updater, whoooo!)
>>  Hm... Does it require users to maintain correct PYTHON_TARGETS in  
>> make.conf? No default/fallback value?
>
> No, I'm a *HUGE* fan of free choice -- I don't know which Python version  
> you want, so select the correct one yourself. It's a one-time choice  
> anyway.
  Just as Michał has pointed it, it is not.

>> It's not big deal, of course, but kind of annoying after so many years  
>> of automatic "build for current Python version unless USE_PYTHON is  
>> set".
> To me it's an advantage :)
  Why? 90% of users just use latest Python available, i.e. 2.7 and 3.2 at  
the moment, and don't really care about actual versions.
python.eclass handles this smoothly, probably using eselect'ed versions.  
Only few people (like me) set USE_PYTHON to suit their needs. Why new  
eclass cannot behave in a similar way? Where's the profit? There's open  
bug already: https://bugs.gentoo.org/show_bug.cgi?id=415575



      parent reply	other threads:[~2012-05-13  6:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 21:13 [gentoo-python] New eclass for Python Krzysztof Pawlik
2012-02-29  5:13 ` Mike Gilbert
2012-02-29  8:11 ` Dirkjan Ochtman
2012-03-03  7:59 ` Arfrever Frehtes Taifersar Arahesis
2012-03-25 18:56 ` [gentoo-python] Re: [gentoo-dev] " Krzysztof Pawlik
2012-05-12  9:19 ` [gentoo-python] " Nikolaj Sjujskij
2012-05-12 10:04   ` Krzysztof Pawlik
2012-05-12 17:20     ` Michał Górny
2012-05-12 20:32       ` Mike Gilbert
2012-05-13 19:57         ` Dirkjan Ochtman
2012-05-14 16:12           ` Krzysztof Pawlik
2012-05-14 17:42             ` Nikolaj Sjujskij
2012-05-14 18:00               ` Krzysztof Pawlik
2012-05-13  6:55     ` Nikolaj Sjujskij [this message]

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.wd7i83rph7emz2@gentoobook.trollsnaetverk \
    --to=sterkrig@myopera.com \
    --cc=gentoo-python@lists.gentoo.org \
    --cc=nelchael@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