On 05/12/2012 01:20 PM, Michał Górny wrote:
> On Sat, 12 May 2012 12:04:36 +0200
> Krzysztof Pawlik <nelchael@g.o> wrote:
> 
>> On 12/05/12 11:19, Nikolaj Sjujskij wrote:
>>> Den 2012-02-29 01:13:36 skrev Krzysztof Pawlik
>>> <nelchael@g.o>:
>>>
>>>> Hello,
>>>>
>>>> After some work during weekend on Python packages I've decided to
>>>> start a rewrite of Python/distutils eclass for installing Python
>>>> packages. ...
>>>> Highlights:
>>>>  ...
>>>>  - 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.
> 
> It's not a one-time choice. It's rather a new choice every time a new
> major version is introduced, and all users who don't care have to
> update the var to keep it up-to-date. Not that I care much, just
> pointing out.
> 

Why not emulate php/ruby and set a default value in the base profile?
See profiles/base/make.defaults.

I think PYTHON_TARGETS="python2_7 python3_2" would be a reasonable choice.