Skip to content

Conversation

@yuokada
Copy link
Contributor

@yuokada yuokada commented Jan 15, 2021

Python 3.5 was reached end-of-life in 2020. So we can drop python3.5 support.

@cla-bot cla-bot bot added the cla-signed label Jan 15, 2021
@yuokada yuokada mentioned this pull request Jan 15, 2021
@yuokada yuokada requested a review from findepi January 15, 2021 15:16
@findepi findepi requested a review from ebyhr January 15, 2021 16:02
@joshthoward
Copy link
Member

Hey guys. What is the rationale behind dropping Python 3.5 before Python 2?

From this issue, we get roughly 6x the number of 3.5 downloads compared to 2.7.

@yuokada
Copy link
Contributor Author

yuokada commented Jan 16, 2021

To be honest, I don't have the big reason to drop python3.5 support.
Since python3.5 was reached end-of-life, I sent the pr mechanically

One of the reason why dropping python3.5 support is relationship to dependency libraries.
Pytest has already dropped python3.5 support. So we might be unable to run tests on python 3.5 properly in the near future.
https://pypi.org/project/pytest/


And also, we can use some functionalities in python 3.6 or later.
https://docs.python.org/3/whatsnew/3.6.html

@@ -1,5 +1,5 @@
[tox]
envlist = py27,py35,py36,py37,pypy2
envlist = py27,py36,py37,py38,py39,pypy2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to also be adding support for newer versions. Can you create a separate PR for that? It should not be controversial (compared to dropping an old version) and we can merge it right away.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Created
#72

@electrum
Copy link
Member

Since this version is working today, I suggest we keep it for now. We can revisit the decision when there is a need, such as wanting to use new syntax or new dependency versions, or if something stops working. Then we can weigh the positive/negative, whereas dropping it now seems to only be a negative.

@yuokada
Copy link
Contributor Author

yuokada commented Jan 17, 2021

@electrum I see. I will close the pr.

@yuokada yuokada closed this Jan 17, 2021
@findepi
Copy link
Member

findepi commented Jan 17, 2021

Hey guys. What is the rationale behind dropping Python 3.5 before Python 2?

From this issue, we get roughly 6x the number of 3.5 downloads compared to 2.7.

@joshthoward
there are two reasons

  • in my not so intensive python development in past 2-3 years i've witnessed problems present in 3.5 and fixed in 3.6. Enough for me to think there is little value supporting Python 3.5 (this is based on memory though)
    • on the other hand, python 2.7 is very solid (even though no longer supported)
  • there is clean upgrade path for users from Python 3.5 to 3.6+
    • this is a big difference between 3.5 and 2.7

i did not know the download numbers when approving.
Knowing the numbers, I would still consider removing 3.5 support for the reasons outlined above, but i can be perhaps convinced to think differently.

@yuokada yuokada deleted the drop-py35 branch September 27, 2024 02:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

4 participants