-
Notifications
You must be signed in to change notification settings - Fork 7
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
Investigate piwheels.org to let users install non-pure Python packages #139
Comments
I did a test with two packages that have native dependencies: The packages and their dependencies installed successfully. However, I got errors when trying to actually use the packages. It looks like some shared library files are still unable to be found:
|
Hmm, thanks for testing that. Just having skimmed those error messages (and not having done any real investigation on this, so take this with a grain of salt), the libc error looks concerning. I wonder if we're on musl whereas piwheels is assuming glibc, or something. If so, we might be able to work around that with buildroot changes. But the fundamental underlying problem that that would point to is piwheels explicitly being specifically for Raspberry Pi OS, whereas we are definitely not running Raspberry Pi OS.
|
Our root partition is apparently very low on space (Opentrons/opentrons#8184).
Some of our space is currently wasted on big packages like
pandas
(#61). We don't actually needpandas
in the root partition; we include it there because users sometimes need it, and it's prohibitively difficult for them topip install
on their own to the big user partition.pip install
fails because of some combination of the package depending on native libraries, and requiring a working compiler.Instead of us continuing to keep packages like this in our root partition, we might be able to get
pip install
to work by configuringpip
to use https://www.piwheels.org/, a community-maintained repository of Python wheel builds specifically for the Raspberry Pi.pandas
we'd like to offloadThe text was updated successfully, but these errors were encountered: