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

Remove support for python3.8 #3770

Merged
merged 1 commit into from Dec 5, 2022
Merged

Remove support for python3.8 #3770

merged 1 commit into from Dec 5, 2022

Conversation

ssbarnea
Copy link
Member

@ssbarnea ssbarnea commented Dec 5, 2022

No description provided.

@ssbarnea ssbarnea removed the bug label Dec 5, 2022
@github-actions github-actions bot added the bug label Dec 5, 2022
@ssbarnea ssbarnea merged commit ea430fc into ansible:main Dec 5, 2022
@ssbarnea ssbarnea deleted the fix/v5 branch December 5, 2022 19:55
@ssbarnea ssbarnea removed the bug label Dec 5, 2022
@dalepotter
Copy link

Out of interest, what is the thinking behind this, given py37 is EOL in 2023-06-27, and py38 over a year later (2024-10)?

@ssbarnea
Copy link
Member Author

ssbarnea commented Jan 3, 2023

@dalepotter That is bringing molecule in sync with other projects such ansible-core and ansible-lint, which already require py39 or newer. Main reason for this is to ease maintenance, so we can focus on fixing bugs than covering older versions of python. Each extra versions we support adds considerable costs, human time in particular.

PS. When me mention supported, we mean fully-supported. A version that only gets security updates does not count as supported from our point of view. Think that you face a serious bug, nobody will help you merge a fix for it if that is not related to security for py37. For this reason alone, we cannot really say that we provide more support than whatever is provided by the upstream dependency (python in this case).

I also observe that you never contributed to molecule project, maybe if you can spend some time and become an active contributor, we might be able to support older pythons for longer.

While we do not use maintenance branches with molecule, that might change in the future, which will allow people to backport important fixed to older versions. Still, that need active community contributors in order to happen.

@dalepotter
Copy link

@ssbarnea thanks for clarifying the thinking - I certainly agree that it would not make sense to maintain support for versions which themselves are not supported by ansible-core.

@ssbarnea ssbarnea added this to the 4.0.0 milestone Jan 4, 2023
@ssbarnea ssbarnea added enhancement and removed bug labels Jan 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants