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.

Sign up for GitHub

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

Jump to bottom

Drop support for Python 3.8 and 3.9 #14638

Closed
jeremystretch opened this issue Dec 29, 2023 · 1 comment
Closed

Drop support for Python 3.8 and 3.9 #14638

jeremystretch opened this issue Dec 29, 2023 · 1 comment
Assignees
@jeremystretch
Labels
breaking change This change modifies or removes some previously documented functionality status: accepted This issue has been accepted for implementation type: deprecation Removal of existing functionality or behavior
Milestone
v4.0

Comments

@jeremystretch
Copy link
Member

Proposed Changes

Increase the minimum supported Python version from 3.8 to 3.10. Remove tests for Python <3.10.

Justification

We'll be adopting Django 5.0 in NetBox v4.0 (see #14637), which requires Python 3.10 or later.

Additionally, Python versions earlier than 3.11 are no longer receiving bug fixes per the Python release cycle.

Impact

NetBox deployments running Python 3.9 or earlier will need to upgrade their Python version to 3.10 or later.
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: deprecation Removal of existing functionality or behavior labels Dec 29, 2023
@jeremystretch jeremystretch added this to the v4.0 milestone Dec 29, 2023
@ekrichbaum
Copy link

I'm all for it and don't see any glaring issues up to and including 3.11. 3.12 opens a lot of cases in downstreams of downstreams to need updates or unpinning of specific older versions.

@jeremystretch jeremystretch self-assigned this Jan 3, 2024
jeremystretch added a commit that referenced this issue Jan 3, 2024
@jeremystretch
Closes #14638: Drop support for Python 3.8 and 3.9
58f7600
@jeremystretch jeremystretch mentioned this issue Jan 3, 2024
Merged
jeremystretch added a commit that referenced this issue Jan 3, 2024
@jeremystretch
Closes #14638: Drop support for Python 3.8 and 3.9
7bedf48
jeremystretch added a commit that referenced this issue Jan 4, 2024
@jeremystretch
#14638: Check for Python 3.10 or later
fb7d483
jeremystretch added a commit that referenced this issue Jan 9, 2024
@jeremystretch
Closes #14638: Drop support for Python 3.8 and 3.9
796247c
jeremystretch added a commit that referenced this issue Jan 9, 2024
@jeremystretch
#14638: Check for Python 3.10 or later
9266dc6
jeremystretch added a commit that referenced this issue Jan 10, 2024
@jeremystretch
Changelog for #14092, #14637, #14638, #14657, #14658, #14672
f819933
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 5, 2024
@jeremystretch jeremystretch added breaking change This change modifies or removes some previously documented functionality type: deprecation Removal of existing functionality or behavior and removed type: deprecation Removal of existing functionality or behavior labels May 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
breaking change This change modifies or removes some previously documented functionality status: accepted This issue has been accepted for implementation type: deprecation Removal of existing functionality or behavior
Projects
None yet
Milestone
v4.0
Development

No branches or pull requests
2 participants
@ekrichbaum @jeremystretch