This repository was archived by the owner on Nov 12, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 985
remove deprecated ez_setup.py; update install instructions (fixes #91) #101
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The instructions are missing python-pip/python3-pip (at least in my Raspbian python-dev/python3-dev does not have it as dependency).
However installing python-pip or python3-pip takes care of installing build-essentials, python-dev/python3-dev and all the rest of the stuff.
As the instructions are for microcomputers, I think it's best to save as much space as possible. And in the end, the less software the user has installed, smaller the risk of having vulnerabilities, so IMHO it's best to fully separate python2 and python3 instructions.
On the other hand, I am not really sure
sudo python -m pip install --upgrade pip setuptools wheelis needed for everyone. At my raspbian it's not required to install using pip (but I am not removing from the proposal anyway).So my proposal would be:
Installing
Dependencies
For all platforms (Raspberry Pi and Beaglebone Black) make sure your system is able to compile and download Python extensions with pip:
On Raspbian or Beaglebone Black's Debian/Ubuntu image you can ensure your system is ready by running one or two of the following sets of commands:
Python2:
Python3:
Install with pip
Use
pipto install from PyPI.Python2:
Python3:
Compile and install from the repository
First download the library source code from the GitHub releases page, unzipping the archive, and execute:
Python2:
cd Adafruit_Python_DHT sudo python setup.py installPython3:
cd Adafruit_Python_DHT sudo python3 setup.py installYou could also git clone the repository if you want to test an unreleased version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested the instructions above, and everything seems to be working fine on Raspbian, even compiling locally from the
remove_ez_setupbranch.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the quality feedback. I'll tweak instructions a bit and merge.