Re: [gentoo-portage-dev] [PATCH] officially drop support for python 2.6, 3.1, and 3.2
On 02 Jun 2015 06:49, Alexander Berntsen wrote: On 02/06/15 06:42, Mike Frysinger wrote: the portage ebuild dropped support: python 3.1: 21 months ago python 2.6: 10 months ago python 3.2: 8 weeks ago the python team itself no longer supports these versions either and it's not possible to install other modules using them. they're already forcing you to pick 2.7 or 3.3+. You make a compelling case here. plus, i'm not talking about changing existing releases, just new ones, which means it's going to be a while before people are completely impacted. I realise that. Anything else would be stupid. at some point we have to move forward and the shims for 2.6/3.1/3.2 are holding us back now. 2.6 is obvious enough, but 3.1 3.2 are a pain due to the unicode differences. conversely, py2.7 and py3.3+ have the same unicode literal format. I agree on all points. So I think this patch would be fine to merge. I'd like Brian to chime in, but I'm a tentative +1. dol-sen but yeah, I don't see a problem in dropping them zmedico yeah dol-sen especially since gkeys is not 3.2 capable dol-sen and I'm starting to integrate it in portage zmedico those pythons are ancient -mike signature.asc Description: Digital signature
Re: [gentoo-portage-dev] [PATCH] officially drop support for python 2.6, 3.1, and 3.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 30/05/15 16:58, Mike Frysinger wrote: We no longer support these in the ebuild and don't want to waste time implementing compatibility shims for them. In principle I don't mind this at all. However, should we do some sort of survey? Maybe a forum poll or something to see if someone desperately needs them? - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJVbMupAAoJENQqWdRUGk8BdtMQALoiCoB56KKAPA8MQs+VM9L6 kuQyg02ihr3VuhV9ztU08D7BbQtBM3SL0/yglJ1uGKnBy2LuVaB6Mj97sWi7brRO pvoo/EWaaW68nclBsiL2EohXkQEa+OVi58psugHXSONQi+p9bpyxYfUrVteFVBo3 6GwM6ylmplLWVvNfGwl/GKCkIZrtCs7G7wmbhla3vXYP+ymvA5eAHc5O37GtzM5x qXVb7ItTHlaqBMySk1yjzgxUfOl16GkCiEtqckQXGzN4l0uKczFjSfAbyUGhD/GP LcjV2R2BDlUkD8n++oeJYdZbQNg8TXoz3UfJdSIZK4Q4O2I8FpAG96QrzGrICDyM GDB4hz2hqfcEFqgiygcp87jsdw5Iu/e2qO3/BvarOo20E63Rlqsa9IhU4i4hWXGe Xm8GecdM3e7mchXUsEzL6bYD9JPOPwH+29JypQOJ9i2ZVGTnnxvcpq7zbrV5u/Wu pBC90XqkFdyogMADhgHJXyYQIa0t2Cfh2gpObKn2oTtV5v+LsHNgYn/eip4C1gsZ 3cR7RpCYNrxJmk2Dh8eNUEsqTg8y/u1M7/d8lRGn8+WrvSjcdtGV7XoQRoJyb14U aiS7DFuslsl/8uDMZAKbeW8PfeK5dgf7q1tDiQvtAg9gZRqa8P4YaMcBrcI6N6Fj jx5jSE4UNVJJu/EVeKcr =XUJY -END PGP SIGNATURE-
Re: [gentoo-portage-dev] [PATCH] officially drop support for python 2.6, 3.1, and 3.2
On 01 Jun 2015 23:16, Alexander Berntsen wrote: On 30/05/15 16:58, Mike Frysinger wrote: We no longer support these in the ebuild and don't want to waste time implementing compatibility shims for them. In principle I don't mind this at all. However, should we do some sort of survey? Maybe a forum poll or something to see if someone desperately needs them? the portage ebuild dropped support: python 3.1: 21 months ago python 2.6: 10 months ago python 3.2: 8 weeks ago the python team itself no longer supports these versions either and it's not possible to install other modules using them. they're already forcing you to pick 2.7 or 3.3+. plus, i'm not talking about changing existing releases, just new ones, which means it's going to be a while before people are completely impacted. at some point we have to move forward and the shims for 2.6/3.1/3.2 are holding us back now. 2.6 is obvious enough, but 3.1 3.2 are a pain due to the unicode differences. conversely, py2.7 and py3.3+ have the same unicode literal format. -mike signature.asc Description: Digital signature
[gentoo-portage-dev] [PATCH] officially drop support for python 2.6, 3.1, and 3.2
We no longer support these in the ebuild and don't want to waste time
implementing compatibility shims for them.
---
.travis.yml | 2 --
DEVELOPING | 8
README | 2 +-
runtests.sh | 4 ++--
4 files changed, 7 insertions(+), 9 deletions(-)
diff --git a/.travis.yml b/.travis.yml
index 69e1659..8a86aa6 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -1,8 +1,6 @@
language: python
python:
-- 2.6
- 2.7
-- 3.2
- 3.3
- 3.4
- pypy
diff --git a/DEVELOPING b/DEVELOPING
index 55470d8..0b0bb60 100644
--- a/DEVELOPING
+++ b/DEVELOPING
@@ -8,10 +8,10 @@ bad habits that exist in the current codebase.
Python Version
--
-Python 2.6 is the minimum supported version, since it is the first
-version to support Python 3 syntax. All exception handling should use
-Python 3 'except' syntax, and the print function should be used instead
-of Python 2's print statement (from __future__ import print_function).
+Python 2.7 is the minimum supported version as it eases 3.x compatibility.
+All exception handling should use Python 3 'except' syntax, and the print
+function should be used instead of Python 2's print statement (use from
+__future__ import print_function everywhere).
Dependencies
diff --git a/README b/README
index 5558dde..415a962 100644
--- a/README
+++ b/README
@@ -10,7 +10,7 @@ package managers.
Dependencies
-Python and Bash should be the only hard dependencies. Python 2.6 is the
+Python and Bash should be the only hard dependencies. Python 2.7 is the
minimum supported version.
diff --git a/runtests.sh b/runtests.sh
index 651928f..a7ca101 100755
--- a/runtests.sh
+++ b/runtests.sh
@@ -3,8 +3,8 @@
# Distributed under the terms of the GNU General Public License v2
# These are the versions we care about. The rest are just nice to have.
-PYTHON_SUPPORTED_VERSIONS=2.6 2.7 3.2 3.3 3.4
-PYTHON_VERSIONS=2.6 2.7 pypy 3.1 3.2 3.3 3.4 3.5
+PYTHON_SUPPORTED_VERSIONS=2.7 3.3 3.4
+PYTHON_VERSIONS=2.7 pypy 3.3 3.4 3.5
# has to be run from portage root dir
cd ${0%/*} || exit 1
--
2.4.1
