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 EOL Python versions? #715

Closed
hugovk opened this issue Dec 11, 2017 · 2 comments
Closed

Drop support for EOL Python versions? #715

hugovk opened this issue Dec 11, 2017 · 2 comments

Comments

@hugovk
Copy link
Contributor

hugovk commented Dec 11, 2017

I'd like to suggest pycodestyle only supports non-EOL Python versions.

Python 2.6, 3.2 and 3.3 are EOL and no longer receive security updates.

image

Here's the pip installs for pycodestyle from PyPI for the last month (via pypinfo --percent --pip --markdown pycodestyle pyversion) showing low numbers for the EOL versions.

python_version percent download_count
2.7 49.2% 475,779
3.6 23.7% 229,441
3.5 18.9% 182,682
3.4 6.8% 66,030
3.3 0.6% 5,971
3.7 0.4% 3,927
2.6 0.4% 3,777
3.2 0.0% 317

https://github.com/PyCQA/pycodestyle/blob/master/docs/developer.rst#direction says:

  • Python 2.6 support is still deemed important.

This was added two years ago (#460), is this still the case?

Some other PyCQA projects are planning on ending all Python 2 support around mid-2018 when Python 3.7 is due out (PyCQA/meta#19).

@sigmavirus24
Copy link
Member

@hugovk please stop spamming PyCQA projects with this specific information. @IanLee1521 and I have both weighed in on the issue you mention. The fact that you're sending this to every project indicates an attempt to start arguments with the organization and projects over their independent leadership. Please address the specific project owners in the issue you keep linking. If they've already responded, you can assume that the project is going to drop support when it has the time and inclination.

@hugovk
Copy link
Contributor Author

hugovk commented Dec 11, 2017

Apologies, the meta issue is about 2.x and dropping 2.7 before it is EOL in 2020.

This is about 2.x and 3.x versions which are already EOL.

I had checked the meta issue and these two projects aren't specifically mentioned there, nor do I see anything from Ian.

No arguments are sought, I thought these decisions are up to each individual project but I'm not familiar with how things are organised and don't wish to cause problems.

As requested, in the future I'll address people from meta. Sorry again.

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

2 participants