[gentoo-dev] [RFC] A news item covering PYTHON_TARGETS

[gentoo-dev] [RFC] A news item covering PYTHON_TARGETS

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]

Hello,

Since some ebuilds are using that variable already and we still didn't
inform most of our users if and how they should set it, I'd like to
commit the following news item:

Title: PYTHON_TARGETS deployment
Author: Michał Górny <mgorny@gentoo.org>
Content-Type: text/plain
Posted: 2012-10-29
Revision: 1
News-Item-Format: 1.0

Lately, a new Python eclasses were deployed and the way of supporting
multiple Python implementations changes with ebuilds being migrated
to them. While before the implementations being installed were used
by default, the migrated packages will instead use explicit choice based
on PYTHON_TARGETS USE flags. This may require action from some of our
users.

If you are running a modern system with Python 2.7 & 3.2, and you didn't
set USE_PYTHON, then you don't have to do anything. The defaults
will fit you.

Otherwise, you will want to set PYTHON_TARGETS in your make.conf file.
This is a regular USE_EXPAND variable listing requested Python
implementations like:

	PYTHON_TARGETS="python2_7 python3_2 pypy1_9 jython2_5"

The variable should list all requested Python implementations.
A complete list of possible values can be obtained using a command like:

	emerge -1pv dev-python/python-exec

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

[gentoo-dev] Re: [RFC] A news item covering PYTHON_TARGETS

[Mike Gilbert]

On Mon, Oct 29, 2012 at 10:45 AM, Michał Górny <mgorny@gentoo.org> wrote:
> Hello,
>
> Since some ebuilds are using that variable already and we still didn't
> inform most of our users if and how they should set it, I'd like to
> commit the following news item:
>
> Title: PYTHON_TARGETS deployment
> Author: Michał Górny <mgorny@gentoo.org>
> Content-Type: text/plain
> Posted: 2012-10-29
> Revision: 1
> News-Item-Format: 1.0
>
> Lately, a new Python eclasses were deployed and the way of supporting
> multiple Python implementations changes with ebuilds being migrated
> to them. While before the implementations being installed were used
> by default, the migrated packages will instead use explicit choice based
> on PYTHON_TARGETS USE flags. This may require action from some of our
> users.
>
> If you are running a modern system with Python 2.7 & 3.2, and you didn't
> set USE_PYTHON, then you don't have to do anything. The defaults
> will fit you.
>
> Otherwise, you will want to set PYTHON_TARGETS in your make.conf file.
> This is a regular USE_EXPAND variable listing requested Python
> implementations like:
>
>         PYTHON_TARGETS="python2_7 python3_2 pypy1_9 jython2_5"
>
> The variable should list all requested Python implementations.
> A complete list of possible values can be obtained using a command like:
>
>         emerge -1pv dev-python/python-exec
>

Good idea to inform users.

Is there a way to have this news item go away, say after a year or so?
Every time I do a fresh install, I get hit with a couple of
"perpetual" news items, and it is a little annoying.

[gentoo-dev] Re: [RFC] A news item covering PYTHON_TARGETS

[Duncan]

Michał Górny posted on Mon, 29 Oct 2012 15:45:01 +0100 as excerpted:

> Title: PYTHON_TARGETS deployment

[snip]

> Lately, a new Python eclasses were deployed and the way of supporting
> multiple Python implementations changes with ebuilds being migrated to
> them. While before the implementations being installed were used by
> default, the migrated packages will instead use explicit choice based on
> PYTHON_TARGETS USE flags. This may require action from some of our
> users.

That paragraph needs help. Try this:

Recently, new python eclasses were deployed.  As ebuilds migrate, the way 
they support multiple python implementations will change.  The previous 
method built support for all installed python implementations.  The new 
method uses the PYTHON_TARGETS USE flags to explicitly name the 
implementations that support should be built for.

> If you are running a modern system with Python 2.7 & 3.2, and you didn't
> set USE_PYTHON, then you don't have to do anything. The defaults will
> fit you.

Fewer changes in this paragraph.  Try this:

If you are running a modern system with Python 2.7 and 3.2 and you 
haven't set USE_PYTHON, you don't need to do anything.  The defaults will 
continue to work just as they have.


The rest of it looks good to me.  Extra points for the specific examples, 
both of PYTHON_TARGETS and of a suitable command-line to get a list of 
all possibilities. =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

Re: [gentoo-dev] Re: [RFC] A news item covering PYTHON_TARGETS

[Michael Mol]

[-- Attachment #1: Type: text/plain, Size: 927 bytes --]

On Mon, Oct 29, 2012 at 1:01 PM, Duncan <1i5t5.duncan@cox.net> wrote:

> Michał Górny posted on Mon, 29 Oct 2012 15:45:01 +0100 as excerpted:
>
> > Title: PYTHON_TARGETS deployment
>
> [snip]
>
> > Lately, a new Python eclasses were deployed and the way of supporting
> > multiple Python implementations changes with ebuilds being migrated to
> > them. While before the implementations being installed were used by
> > default, the migrated packages will instead use explicit choice based on
> > PYTHON_TARGETS USE flags. This may require action from some of our
> > users.
>
> That paragraph needs help. Try this:
>
> Recently, new python eclasses were deployed.  As ebuilds migrate, the way
>

Recently, a new python eclass was deployed.

or

Recently, a few new python eclasses were deployed.

or even

Recently, a few python eclasses were deployed.

And then capitalize Python.

-- 
:wq

[-- Attachment #2: Type: text/html, Size: 1399 bytes --]

Re: [gentoo-dev] [RFC] A news item covering PYTHON_TARGETS

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]

On Mon, 29 Oct 2012 15:45:01 +0100
Michał Górny <mgorny@gentoo.org> wrote:

> Since some ebuilds are using that variable already and we still didn't
> inform most of our users if and how they should set it, I'd like to
> commit the following news item:

Thank you for all your suggestions, and especially Duncan for wording
the hardest paragraph for me ;). I've also tried to make the remaining
ones clearer.

Title: PYTHON_TARGETS deployment
Author: Michał Górny <mgorny@gentoo.org>
Content-Type: text/plain
Posted: 2012-10-29
Revision: 1
News-Item-Format: 1.0

Recently, a few new Python eclasses were deployed. As ebuilds migrate,
the way they support multiple Python implementations will change.
The previous method built Python modules for all currently installed
Python implementations. The new one uses the PYTHON_TARGETS USE flags to
explicitly name the implementations the modules shall be built for.

If you are running a modern system with Python 2.7 & 3.2 being the only
installed Python implementations, then you don't have to do anything.
The defaults will simply fit you, and let you keep your system
up-to-date when new Python versions are deployed.

However, if you'd like to use another set of Python implementations, you
will want to set PYTHON_TARGETS in your make.conf file appropriately.
This variable names the enabled implementations in the standard way
common to all USE_EXPAND variables.

For example, a setup enabling all major Python implementations would
look like:

	PYTHON_TARGETS="python2_7 python3_2 pypy1_9 jython2_5"

The variable should list all Python implementations which are going to
be used on the system; missing a particular value there will result
in missing Python modules.

A complete list of all possible values can be obtained using a command
equivalent to the following:

	emerge -1pv dev-python/python-exec

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

[gentoo-dev] Re: [RFC] A news item covering PYTHON_TARGETS

[Duncan]

Michał Górny posted on Mon, 29 Oct 2012 22:50:09 +0100 as excerpted:

> Thank you for all your suggestions, and especially Duncan for wording
> the hardest paragraph for me ;). I've also tried to make the remaining
> ones clearer.

That's clear enough if it were water you could bottle and sell it! =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

Re: [gentoo-dev] Re: [RFC] A news item covering PYTHON_TARGETS

[Petteri Räty]

[-- Attachment #1: Type: text/plain, Size: 532 bytes --]

On 29.10.2012 18:15, Mike Gilbert wrote:

>>
> 
> Good idea to inform users.
> 
> Is there a way to have this news item go away, say after a year or so?
> Every time I do a fresh install, I get hit with a couple of
> "perpetual" news items, and it is a little annoying.
> 

News items were designed to be deleted when they are not deleted.
Unfortunately Portage used to crash when that was first tried. I think
it's been quite a long time since that was fixed so it could be safe to
try again.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 897 bytes --]