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

pip3 instead of pip in install docs #875

New Issue
Closed
opened 2025-12-29 16:26:34 +01:00 by adam · 6 comments
adam commented 2025-12-29 16:26:34 +01:00
Owner
Copy Link

Originally created by @mzac on GitHub (Apr 19, 2017).

Issue type: Bug report

Python version: 3
NetBox version: 1.9.5

While reading the install docs I decided to use Python 3 however getting to the step of 'pip install -r requirements.txt' this failed, the documentation needs to have 'pip3 install -r requirements.txt' added if you are using python3.

Originally created by @mzac on GitHub (Apr 19, 2017). <!-- Please note: GitHub issues are to be used only for feature requests and bug reports. For installation assistance or general discussion, please join us on the mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please indicate "bug report" or "feature request" below. Be sure to search the existing set of issues (both open and closed) to see if a similar issue has already been raised. --> ### Issue type: Bug report <!-- If filing a bug, please indicate the version of Python and NetBox you are running. (This is not necessary for feature requests.) --> **Python version:** 3 **NetBox version:** 1.9.5 <!-- If filing a bug, please record the exact steps taken to reproduce the bug and any errors messages that are generated. If filing a feature request, please precisely describe the data model or workflow you would like to see implemented, and provide a use case. --> While reading the install docs I decided to use Python 3 however getting to the step of 'pip install -r requirements.txt' this failed, the documentation needs to have 'pip3 install -r requirements.txt' added if you are using python3.
adam added the type: bug label 2025-12-29 16:26:34 +01:00
adam closed this issue 2025-12-29 16:26:34 +01:00
adam commented 2025-12-29 16:26:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 19, 2017):

Can you please provide a detailed account of the installation procedure you followed?

@jeremystretch commented on GitHub (Apr 19, 2017): Can you please provide a detailed account of the installation procedure you followed?
adam commented 2025-12-29 16:26:35 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Apr 19, 2017):

There was a discussion in the Google group about this as well:

https://groups.google.com/forum/#!topic/netbox-discuss/Sc3Bp2glPqs

@bellwood commented on GitHub (Apr 19, 2017): There was a discussion in the Google group about this as well: https://groups.google.com/forum/#!topic/netbox-discuss/Sc3Bp2glPqs
adam commented 2025-12-29 16:26:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 21, 2017):

Turns out there are several issues when only Python 3 is installed (on Ubuntu, at least).

  • Ubuntu has different packages for psycopg2 under Python 2/3
  • Ubuntu does not provide /usr/bin/python (only /usr/bin/python3)
  • Ubuntu does not provide /usr/bin/pip (only /usr/bin/pip3)
@jeremystretch commented on GitHub (Apr 21, 2017): Turns out there are several issues when only Python 3 is installed (on Ubuntu, at least). * Ubuntu has different packages for psycopg2 under Python 2/3 * Ubuntu does not provide `/usr/bin/python` (only `/usr/bin/python3`) * Ubuntu does not provide `/usr/bin/pip` (only `/usr/bin/pip3`)
adam commented 2025-12-29 16:26:35 +01:00
Author
Owner
Copy Link

@mzac commented on GitHub (Apr 21, 2017):

Glad you found the fix :) I'm still quite new to python so I wasn't sure if I was missing something but it looks like I'll give it a retry on python 3 instead of python 2 now...

@mzac commented on GitHub (Apr 21, 2017): Glad you found the fix :) I'm still quite new to python so I wasn't sure if I was missing something but it looks like I'll give it a retry on python 3 instead of python 2 now...
adam commented 2025-12-29 16:26:35 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Apr 21, 2017):

Prior to releasing v2.0 which will require Python3 we should make sure that the docs for both Ubuntu and RHEL/Cent are firm otherwise I can foresee a large inrush of related issues.

@bellwood commented on GitHub (Apr 21, 2017): Prior to releasing v2.0 which will require Python3 we should make sure that the docs for both Ubuntu and RHEL/Cent are firm otherwise I can foresee a large inrush of related issues.
adam commented 2025-12-29 16:26:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 21, 2017):

I've worked through a few Ubuntu and CentOS installations using Python 3 and I think this has been sorted. I'm going to close out this issue but please feel free to re-open or open a new one as appropriate for any outstanding issues.

Prior to releasing v2.0 which will require Python3

NetBox v2.0 won't require Python3 (although it's strongly encouraged). We'll still be on Django 1.11. Django 2.0 will drop support for Python3, but we probably won't move to Django 2.0 until sometime in early 2018. No promises, though.

@jeremystretch commented on GitHub (Apr 21, 2017): I've worked through a few Ubuntu and CentOS installations using Python 3 and I think this has been sorted. I'm going to close out this issue but please feel free to re-open or open a new one as appropriate for any outstanding issues. > Prior to releasing v2.0 which will require Python3 NetBox v2.0 won't _require_ Python3 (although it's strongly encouraged). We'll still be on Django 1.11. Django 2.0 will drop support for Python3, but we probably won't move to Django 2.0 until sometime in early 2018. No promises, though.
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 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#875
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?