Skip to content

End support for Python 3.7 and 3.8? #448

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

Open
tomschr opened this issue Nov 4, 2024 · 3 comments
Open

End support for Python 3.7 and 3.8? #448

tomschr opened this issue Nov 4, 2024 · 3 comments
Labels
Infra All about infrastructure (GitHub Action, project build etc.) Release_3.x.y Only for the major release 3 Release_4.x.y Only for the major release 4

Comments

@tomschr
Copy link
Member

tomschr commented Nov 4, 2024

Situation

According to the Status of Python versions, Python 3.7 and 3.8 are already "end-of-life".

To Reproduce

See table in "unsupported versions":

  • Python 3.7: PEP 537, end of life 2023-06-27
  • Python 3.8: PEP 569, end of life 2024-10-07

Expected Behavior

The unsupported Python versions are subject to be removed in the next major release of semver.

@python-semver/reviewers what do you think?

Environment

not relevant

Additional context

Relevant poll #449

@tomschr tomschr added Release_3.x.y Only for the major release 3 Infra All about infrastructure (GitHub Action, project build etc.) Release_4.x.y Only for the major release 4 labels Nov 4, 2024
@tomschr tomschr pinned this issue Dec 14, 2024
@tomschr tomschr changed the title End of life for Python 3.7 and 3.8 End support for Python 3.7 and 3.8? Dec 14, 2024
@eirnym
Copy link

eirnym commented Jan 22, 2025

In my personal opinion, it's worth a while to just drop the support without asking. Python 3.7 and 3.8 users would just use last compatible version.

I don't know if you have any statistics on pypi.org for which python version package has been requested though. If you have such statistics, it's worth a while to look into that

@tomschr
Copy link
Member Author

tomschr commented Jan 22, 2025

Thanks @eirnym for your ideas! I used this to get a clearer picture of the downloads, so I've used pypistats. This is the result:

$ pypistats python_minor semver
┌──────────┬─────────┬─────────────┐
│ category │ percent │   downloads │
├──────────┼─────────┼─────────────┤
│ 3.9      │  26.82% │  39,537,839 │
│ 3.10     │  17.87% │  26,341,633 │
│ 3.11     │  16.78% │  24,733,356 │
│ 3.6      │  13.58% │  20,010,727 │
│ 3.12     │   7.62% │  11,235,062 │
│ null     │   7.19% │  10,602,594 │
│ 3.8      │   7.01% │  10,335,207 │
│ 3.7      │   2.40% │   3,543,235 │
│ 3.13     │   0.56% │     822,993 │
│ 2.7      │   0.15% │     228,150 │
│ 3.14     │   0.01% │       8,658 │
│ 3.5      │   0.00% │       1,293 │
│ 3.4      │   0.00% │           4 │
│ Total    │         │ 147,400,751 │
└──────────┴─────────┴─────────────┘

Date range: 2024-07-25 - 2025-01-21

As "category" refers to the Python version, it looks like 3.7 and 3.8 is still being used. Maybe I consider of removing 3.7.

@eirnym
Copy link

eirnym commented Jan 23, 2025

Nice statistics.

Python 3.8 will gone soon as well quite soon, it's just after EOL and not every venv is switched over to higher python versions. (As you can observe even in Python 2.7 usage)

Thus, in my personal opinion, I'd keep support for minor version, but drop for major version. This would ease your development process quite a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Infra All about infrastructure (GitHub Action, project build etc.) Release_3.x.y Only for the major release 3 Release_4.x.y Only for the major release 4
Projects
None yet
Development

No branches or pull requests

2 participants