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 fails when /usr/bin/python3 has too old version or does not exist #3635

New Issue
Closed
opened 2025-12-29 18:30:17 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:30:17 +01:00
Owner
Copy Link

Originally created by @jannooo on GitHub (May 5, 2020).

Environment

  • Python version: 3.5 respectively 3.8.2
  • NetBox version: 2.8.1

Steps to Reproduce

  1. run ./upgrade.sh when /usr/bin/python3 does not exist or has an version <= 3.5

Expected Behavior

./upgrade.sh should use /usr/bin/env to determine the right python3 executable

Observed Behavior

./upgrade.sh fails

Originally created by @jannooo on GitHub (May 5, 2020). ### Environment * Python version: 3.5 respectively 3.8.2 * NetBox version: 2.8.1 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a client library such as pynetbox. --> ### Steps to Reproduce 1. run ./upgrade.sh when /usr/bin/python3 does not exist or has an version <= 3.5 ### Expected Behavior ./upgrade.sh should use /usr/bin/env to determine the right python3 executable ### Observed Behavior ./upgrade.sh fails
adam closed this issue 2025-12-29 18:30:17 +01:00
adam commented 2025-12-29 18:30:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 5, 2020):

It is the user's responsibility to install a supported version of Python per the installation and upgrade documentation.

@jeremystretch commented on GitHub (May 5, 2020): It is the user's responsibility to install a supported version of Python per the installation and upgrade documentation.
adam commented 2025-12-29 18:30:18 +01:00
Author
Owner
Copy Link

@jannooo commented on GitHub (May 5, 2020):

Well, what's the problem of using '/usr/bin/env python3' instead of hardcoding '/usr/bin/python3' as suggested in the PR?

As you said the user is responsible for installing the right version, but sometimes it is not possible to install a appropriate version in '/usr/bin/'

@jannooo commented on GitHub (May 5, 2020): Well, what's the problem of using '/usr/bin/env python3' instead of hardcoding '/usr/bin/python3' as suggested in the PR? As you said the user is responsible for installing the right version, but sometimes it is not possible to install a appropriate version in '/usr/bin/'
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
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#3635
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?