public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-dev] [PATCH 02/13] python-utils-r1.eclass: Reorder implementations to semi-ascending order
Date: Sun,  6 Dec 2015 20:03:21 +0100	[thread overview]
Message-ID: <1449428612-20538-3-git-send-email-mgorny@gentoo.org> (raw)
In-Reply-To: <1449428612-20538-1-git-send-email-mgorny@gentoo.org>

Reorder the Python implementations to ascending version order, with
CPython listed first and other implementations in descending preference.

The previous ordering has been used for two reasons:

1. There were packages which supported Python 3.x or PyPy partially but
their documentation builds or test functions required CPython 2.x.
The specific ordering caused python_export_best (the predecessor of
python_setup) to use CPython 2.x for those tasks. This is now replaced
by explicit implementation restrictions in python_setup.

2. PyPy setup runs were usually slower than CPython, and CPython 3.x
runs were often slower due to 2to3 calls. Combined with parallel build
runs, this ordering caused slower builds to start earlier and sometimes
resulted in more efficient use of threads. However, nowadays we no
longer do parallel builds.

Therefore, it seems reasonable to finally reorder the implementations
into a more intuitive order.
---
 eclass/python-utils-r1.eclass | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/eclass/python-utils-r1.eclass b/eclass/python-utils-r1.eclass
index 0bce6a9..3ea23a8 100644
--- a/eclass/python-utils-r1.eclass
+++ b/eclass/python-utils-r1.eclass
@@ -41,10 +41,10 @@ inherit toolchain-funcs
 # @DESCRIPTION:
 # All supported Python implementations, most preferred last.
 declare -g -r _PYTHON_ALL_IMPLS=(
-	jython2_5 jython2_7
-	pypy pypy3
-	python3_3 python3_4 python3_5
 	python2_7
+	python3_3 python3_4 python3_5
+	pypy pypy3
+	jython2_5 jython2_7
 )
 
 # @FUNCTION: _python_impl_supported
-- 
2.6.3



  parent reply	other threads:[~2015-12-06 19:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06 19:03 [gentoo-dev] [PATCHES] python-r1 suite clean up & impl reorder Michał Górny
2015-12-06 19:03 ` [gentoo-dev] [PATCH 01/13] python-utils-r1.eclass: Mark _PYTHON_ALL_IMPLS read-only Michał Górny
2015-12-06 19:03 ` Michał Górny [this message]
2015-12-08  8:19   ` [gentoo-dev] [PATCH 02/13] python-utils-r1.eclass: Reorder implementations to semi-ascending order Patrice Clement
2015-12-09 19:24     ` Michał Górny
2015-12-06 19:03 ` [gentoo-dev] [PATCH 03/13] python-any-r1.eclass: Rename global-setting func to match eclass name Michał Górny
2015-12-06 19:03 ` [gentoo-dev] [PATCH 04/13] python-any-r1.eclass: Unset global-setting function after use Michał Górny
2015-12-06 19:03 ` [gentoo-dev] [PATCH 05/13] python-any-r1.eclass: Mark eclass-generated variables read-only Michał Górny
2015-12-06 19:03 ` [gentoo-dev] [PATCH 06/13] python-single-r1.eclass: Unset global-setting function after use Michał Górny
2015-12-06 19:03 ` [gentoo-dev] [PATCH 07/13] python-single-r1.eclass: python_gen_cond_dep(), rename local PYTHON_USEDEP Michał Górny
2015-12-06 19:03 ` [gentoo-dev] [PATCH 08/13] python-single-r1.eclass: Mark eclass-generated variables read-only Michał Górny
2015-12-06 19:03 ` [gentoo-dev] [PATCH 09/13] python-r1.eclass: Unset global-setting function after use Michał Górny
2015-12-06 19:03 ` [gentoo-dev] [PATCH 10/13] python-r1.eclass: Unset local functions " Michał Górny
2015-12-06 19:03 ` [gentoo-dev] [PATCH 11/13] python-r1.eclass: python_gen_cond_dep(), rename local PYTHON_USEDEP Michał Górny
2015-12-06 19:03 ` [gentoo-dev] [PATCH 12/13] python-r1.eclass: Mark eclass-generated variables read-only Michał Górny
2015-12-06 19:03 ` [gentoo-dev] [PATCH 13/13] distutils-r1.eclass: Unset local functions after use Michał Górny
2015-12-07 20:36 ` [gentoo-dev] [PATCHES] python-r1 suite clean up & impl reorder Mike Gilbert
2015-12-07 21:27   ` Michał Górny
2015-12-09 20:45 ` Michał Górny

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=1449428612-20538-3-git-send-email-mgorny@gentoo.org \
    --to=mgorny@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