From: Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org>
To: Gentoo Development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Python-3.2-related changes
Date: Fri, 5 Feb 2010 17:40:00 +0100 [thread overview]
Message-ID: <201002051740.29640.Arfrever@gentoo.org> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 2153 bytes --]
It is planned that ebuilds of Python 3.2 will automatically set Python 3.2 as main active
version of Python. (Currently ebuilds of Python 3.1 do not automatically set Python 3.1
as main active version of Python.) Final release of Python 3.2 is currently scheduled on
2010-12-11, so you have over 10 months for adjusting of your ebuilds.
The following changes should be made in ebuilds of packages supporting only Python 2:
- Dependency on Python 2 should be set correctly. You can specify it directly in
{,R}DEPEND or use PYTHON_DEPEND.
Example:
PYTHON_DEPEND="2"
inherit python
- Miscellaneous actions should be executed with correct version of Python.
- In ebuilds of packages supporting installation for multiple versions of Python,
please remember to disable installation for all versions of Python 3.
(Please do not use python_set_active_version() in ebuilds of these packages.)
Example:
RESTRICT_PYTHON_ABIS="3.*"
- In ebuilds of packages not supporting installation for multiple versions of Python,
set active version of Python using python_set_active_version().
(Please avoid passing precisely specified Python ABI to python_set_active_version().)
Example:
pkg_setup() {
python_set_active_version 2
}
(If given package currently cannot be installed for multiple versions of Python,
but it is theoretically possible (e.g. this package installs .py files into
/usr/lib/pythonX.Y/site-packages and does not install any non-versioned libraries
into /usr/lib), then please try to adjust ebuilds of this package to allow
installation for multiple versions of Python.)
It is recommended to have set a version of Python 3 as main active version of Python
during testing of these changes to ensure that no required change has been missed.
I consider filing bugs for not adjusted packages after some months (e.g in summer).
(Please note that these changes are not required before stabilization of Python 3.1,
so stabilization of Python 3.1 will not be delayed.)
--
Arfrever Frehtes Taifersar Arahesis
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2010-02-05 16:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 16:40 Arfrever Frehtes Taifersar Arahesis [this message]
2010-02-06 10:23 ` [gentoo-dev] Python-3.2-related changes Arfrever Frehtes Taifersar Arahesis
2010-02-06 16:54 ` Mark Loeser
2010-02-08 12:29 ` Arfrever Frehtes Taifersar Arahesis
2010-02-09 8:10 ` Thilo Bangert
2010-02-09 11:14 ` [gentoo-dev] " Duncan
2010-02-06 11:03 ` [gentoo-dev] " Arfrever Frehtes Taifersar Arahesis
2010-02-06 12:14 ` Brian Harring
2010-02-08 16:06 ` Arfrever Frehtes Taifersar Arahesis
2010-02-07 18:43 ` Markos Chandras
2010-02-08 12:14 ` Arfrever Frehtes Taifersar Arahesis
2010-02-07 20:17 ` Zac Medico
2010-02-08 0:20 ` Brian Harring
2010-02-08 12:11 ` Arfrever Frehtes Taifersar Arahesis
2010-03-01 3:13 ` Arfrever Frehtes Taifersar Arahesis
2010-03-01 5:13 ` Max Arnold
2010-03-01 23:06 ` Arfrever Frehtes Taifersar Arahesis
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=201002051740.29640.Arfrever@gentoo.org \
--to=arfrever@gentoo.org \
--cc=gentoo-dev@lists.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