Skip to content
This repository has been archived by the owner on Sep 1, 2023. It is now read-only.

Proposal: Dropping Python 2.6 #410

Closed
breznak opened this issue Nov 13, 2013 · 1 comment
Closed

Proposal: Dropping Python 2.6 #410

breznak opened this issue Nov 13, 2013 · 1 comment

Comments

@breznak
Copy link
Member

breznak commented Nov 13, 2013

Would it be possible to move to python 2.7 as the default (and even break feature parity with python2.6 to take advantage of 2.7)?

For the linux/mac landscape this shouldnt be a problem, as python 2.7 is available there (and sometimes even default).

Many projects still use python 2 (havent shifted to Python 3.x), so it's good to stict there. Also, python 2.7 is the last stage of python2 series [1], so there won't be any puthon2.8. Also it's actively used, so there will be 2.7.y bugfix releases. That makes it ideal target.

Pros:
+drop hacks for py2.6
+reduce Travis build matrix
+python 2.7 is final stage of py2

Cons:
-Grok uses Jython, Jython depends on python 2.5(?)
But now there seems to be a release using python 2.7 (albeit beta!) [2], would it be possible for grok to shift over to using it?

[1] https://mail.python.org/pipermail/python-dev/2010-October/105016.html
[2] http://www.jython.org/

@rhyolight
Copy link
Member

A valid proposal, but this debate needs to happen on the mailing list. Marek, can you please post the issue there?

(Also, Grok does not use jython anymore.)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants