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 Python 3.7 Support #2316

Closed
2 tasks done
bryanculver opened this issue Aug 26, 2022 · 2 comments · Fixed by #3554
Closed
2 tasks done

Drop Python 3.7 Support #2316

bryanculver opened this issue Aug 26, 2022 · 2 comments · Fixed by #3554
Assignees
Labels
type: housekeeping Changes to the application which do not directly impact the end user

Comments

@bryanculver
Copy link
Member

bryanculver commented Aug 26, 2022

Proposed Changes

Drop Python 3.7 support.

Justification

3.7 stops receiving security fixes in July 2023. Dependent libraries may drop support earlier but commonly not soon after.

TODO

  • Remove publish of package & container support
  • Switch default container image to newer version (doesn't have to be 3.8)
@bryanculver bryanculver added the type: housekeeping Changes to the application which do not directly impact the end user label Aug 26, 2022
@itdependsnetworks
Copy link
Contributor

Perhaps as an alternate to this, let's just define the process and put this conversation to bed. Something like this could be good.

  • In the immediate release after Python security will no longer be maintained, Nautobot support will be removed
  • The removal will be in semver Minor versions
  • They will be announced in the release notes

@glennmatthews
Copy link
Contributor

Done in #3554.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: housekeeping Changes to the application which do not directly impact the end user
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants