starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Drop support for Python 3.8 and 3.9 #9011

New Issue
Closed
opened 2025-12-29 20:44:08 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:44:08 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Dec 29, 2023).

Originally assigned to: @jeremystretch on GitHub.

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.

Originally created by @jeremystretch on GitHub (Dec 29, 2023). Originally assigned to: @jeremystretch on GitHub. ### 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](https://docs.djangoproject.com/en/5.0/releases/5.0/#python-compatibility). Additionally, Python versions earlier than 3.11 are no longer receiving bug fixes per the [Python release cycle](https://devguide.python.org/versions/). ### Impact NetBox deployments running Python 3.9 or earlier will need to upgrade their Python version to 3.10 or later.
adam added the status: acceptedtype: deprecationbreaking change labels 2025-12-29 20:44:08 +01:00
adam closed this issue 2025-12-29 20:44:09 +01:00
adam commented 2025-12-29 20:44:09 +01:00
Author
Owner
Copy Link

@ekrichbaum commented on GitHub (Dec 29, 2023):

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.

@ekrichbaum commented on GitHub (Dec 29, 2023): 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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label breaking change status: accepted type: deprecation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9011
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?