-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Freeze all python dependencies in requirements.txt #1320
Comments
On Ubuntu aarch64 this is what I get. They seem accurate and complete. Web UI
OLED
... the Control Board dependencies I cannot extract on this system. pip chokes when trying to build RPi.GPIO C glue code (missing sys/epoll.h etc.). It has to be done on an RPi I think. |
This takes care of Web UI and OLED requirements.txt #1322 |
Done for Web UI, OLED, and common. Control Board is less critical and can be followed up post release. I'll keep this ticket open for now. |
I was tinkering with the control board dependencies and noticed that the RPi.GPIO library no longer is available from the pypi repository via pip on RPi OS. A quick googling suggests that it is distributed as an apt package on RPi OS these days (and allegedly installed by default) — the package named: python3-rpi.gpio I think it should be safe to remove RPi.GPIO from requirements.txt |
This should do it for the control board dependencies. #1398 |
With the debacle with Flask dependencies, we've learned the hard way that implicit python library dependencies aren't reliable. I propose that we
pip freeze
the complete dependency map in requirements.txt for each Python client (presently 22 libraries for the Web UI, for instance.)The text was updated successfully, but these errors were encountered: