Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop support for python 2.6? #175

Closed
ceball opened this issue Jul 16, 2017 · 9 comments
Closed

Drop support for python 2.6? #175

ceball opened this issue Jul 16, 2017 · 9 comments

Comments

@ceball
Copy link
Member

ceball commented Jul 16, 2017

I struggle to remember what's valid in all the different pythons, and thinking about it takes up time. It used to be worthwhile to support multiple versions of Python 2 while people moved between versions and when people relied on their system's python, but those days seem to be gone with everyone converging on Python 2.7 (Python 2.6 hasn't had an update since 2013; https://www.python.org/download/releases/2.6.9/). And it's not like we've kept supporting every version of Python 2 we ever used (we happily dropped 2.5, 2.4, ... etc in the past).

But please comment if you need param to keep working on Python 2.6...

@jlstevens
Copy link
Contributor

Dropping Python 2.6 is fine by me...

@hugovk
Copy link
Contributor

hugovk commented Oct 16, 2017

It's definitely time to drop 2.6, it's getting harder to support with other packages dropping it too. Similarly with 3.2 too.

@ceball
Copy link
Member Author

ceball commented Oct 16, 2017

(I agree that it gets harder to support python 2.6 as your dependencies start dropping it, but param has no dependencies other than python.)

@hugovk
Copy link
Contributor

hugovk commented Oct 16, 2017

(I see quite a few test dependencies :)

@ceball
Copy link
Member Author

ceball commented Oct 16, 2017

If there are any dependencies other than python, that's a mistake: param shouldn't be depending on anything other than python. However, we do enable some extra (entirely optional) features if certain other packages are present (e.g. numpy, ipython).

Please let us know if you are aware of any non-optional dependencies; the automatic testing of param is not currently set up very well (e.g. #189), so something could have slipped in. Thanks!

@hugovk
Copy link
Contributor

hugovk commented Oct 16, 2017

I can see things like pip, coveralls and flake8 being used on Travis CI for testing.

At least current pip 9 deprecates Python 2.6 support, pip 10 won't support it (pypa/pip#3955).

You can see deprecation warnings in the log already:

image

https://travis-ci.org/ioam/param/jobs/288291115#L450

@jbednar
Copy link
Member

jbednar commented Oct 16, 2017

I'm happy to drop Python 2.6 testing; old versions of Param will always stay around for anyone who needs to work with old Python versions.

@ceball
Copy link
Member Author

ceball commented Oct 16, 2017

I can see things like pip, coveralls and flake8 being used on Travis CI for testing.

Speaking from a personal point of view: those are all optional things that param predates. param doesn't depend on pip (the source of the deprecation warning*), coveralls, flake8, travis, setuptools, or anything else: param's just two files (at most) that you can copy into your python project without needing any of the confusing, varied, ever-changing ecosystem of python packaging/testing tools.

* ...a deprecation warning from a python packaging tool of all things - the cheek! ;)

@hugovk
Copy link
Contributor

hugovk commented Oct 28, 2017

See PR #203.

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

No branches or pull requests

4 participants