| 1 |
On 05/12/2012 01:20 PM, Michał Górny wrote: |
| 2 |
> On Sat, 12 May 2012 12:04:36 +0200 |
| 3 |
> Krzysztof Pawlik <nelchael@g.o> wrote: |
| 4 |
> |
| 5 |
>> On 12/05/12 11:19, Nikolaj Sjujskij wrote: |
| 6 |
>>> Den 2012-02-29 01:13:36 skrev Krzysztof Pawlik |
| 7 |
>>> <nelchael@g.o>: |
| 8 |
>>> |
| 9 |
>>>> Hello, |
| 10 |
>>>> |
| 11 |
>>>> After some work during weekend on Python packages I've decided to |
| 12 |
>>>> start a rewrite of Python/distutils eclass for installing Python |
| 13 |
>>>> packages. ... |
| 14 |
>>>> Highlights: |
| 15 |
>>>> ... |
| 16 |
>>>> - uses PYTHON_TARGETS use-expand (no more python-updater, whoooo!) |
| 17 |
>>> Hm... Does it require users to maintain correct PYTHON_TARGETS in |
| 18 |
>>> make.conf? No default/fallback value? |
| 19 |
>> |
| 20 |
>> No, I'm a *HUGE* fan of free choice -- I don't know which Python |
| 21 |
>> version you want, so select the correct one yourself. It's a one-time |
| 22 |
>> choice anyway. |
| 23 |
> |
| 24 |
> It's not a one-time choice. It's rather a new choice every time a new |
| 25 |
> major version is introduced, and all users who don't care have to |
| 26 |
> update the var to keep it up-to-date. Not that I care much, just |
| 27 |
> pointing out. |
| 28 |
> |
| 29 |
|
| 30 |
Why not emulate php/ruby and set a default value in the base profile? |
| 31 |
See profiles/base/make.defaults. |
| 32 |
|
| 33 |
I think PYTHON_TARGETS="python2_7 python3_2" would be a reasonable choice. |
Archives