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

upgrade.sh does not require Python 3.8 #6356

New Issue
Closed
opened 2025-12-29 19:39:47 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:39:47 +01:00
Owner
Copy Link

Originally created by @markkuleinio on GitHub (Apr 14, 2022).

Originally assigned to: @markkuleinio on GitHub.

NetBox version

v3.2.1

Python version

3.8

Steps to Reproduce

  1. Run upgrade.sh on a system with Python 3.7 only

Expected Behavior

upgrade.sh should complain about the minimum required Python version (3.8 for NetBox 3.2)

Observed Behavior

# ./upgrade.sh
Using Python 3.7.3
...
ERROR: Could not find a version that satisfies the requirement Django==4.0.4

so there is no direct error message about the Python version.

In the start of upgrade.sh there is a Python version check but it only checks for 3.7+ while Python 3.8+ is required for NetBox 3.2.

Originally created by @markkuleinio on GitHub (Apr 14, 2022). Originally assigned to: @markkuleinio on GitHub. ### NetBox version v3.2.1 ### Python version 3.8 ### Steps to Reproduce 1. Run `upgrade.sh` on a system with Python 3.7 only ### Expected Behavior `upgrade.sh` should complain about the minimum required Python version (3.8 for NetBox 3.2) ### Observed Behavior ``` # ./upgrade.sh Using Python 3.7.3 ... ERROR: Could not find a version that satisfies the requirement Django==4.0.4 ``` so there is no direct error message about the Python version. In the start of `upgrade.sh` there is a Python version check but it only checks for 3.7+ while Python 3.8+ is required for NetBox 3.2.
adam added the type: bugstatus: accepted labels 2025-12-29 19:39:47 +01:00
adam closed this issue 2025-12-29 19:39:47 +01:00
adam commented 2025-12-29 19:39:47 +01:00
Author
Owner
Copy Link

@markkuleinio commented on GitHub (Apr 14, 2022):

PR ready to be submitted if issue is accepted.

@markkuleinio commented on GitHub (Apr 14, 2022): PR ready to be submitted if issue is accepted.
adam commented 2025-12-29 19:39:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 14, 2022):

We do have the logic in there but it currently only checks for v3.7+, so it should be an easy tweak. Thanks!

@jeremystretch commented on GitHub (Apr 14, 2022): We do have the logic in there but it currently only checks for v3.7+, so it should be an easy tweak. Thanks!
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 status: accepted type: bug
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#6356
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?