You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
@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.
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.
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.
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.https://github.com/PyCQA/pycodestyle/blob/master/docs/developer.rst#direction says:
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).
The text was updated successfully, but these errors were encountered: