Skip to content

Clarify potential issue with dynamic python library #236

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

Merged
merged 2 commits into from
Feb 28, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -160,6 +160,13 @@ configuration as json. We parse the json and use the output to attempt to find
the `libpython3.Xm.so` shared library so for example if we are loading python
3.6 we look for `libpython3.6m.so` on Linux or `libpython3.6m.dylib` on the Mac.

If we are unable to find a dynamic library such as `libpythonx.y.so` or `libpythonx.z.dylib`,
it may be because Python is statically linked and the library is not present at all.
This is dependent on the operating system and installation, and it is not always possible to detect it.
In this case, we will receive an error message saying "Failed to find a valid python library!".
To fix this, you may need to install additional OS packages or manually set the precise library location during `py/initialize!`.


This pathway has allowed us support Conda albeit with some work. For examples
using Conda, check out the facial rec repository a)bove or look into how we
[build](scripts/build-conda-docker)
Expand Down