-
Notifications
You must be signed in to change notification settings - Fork 10
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
Basilisk forces the use of potentially incompatible Conda binaries #191
Comments
I forgot to tag the commit but we have the dev branch allowing to specify a path to python (e.g. Lines 265 to 272 in 99ae8b7
The environment necessary for installing the default environment that |
Is there a single location where a default for |
oh you mean if you need to specify the path everytime you call a method that use reticulate ? Perhaps you may need something like:
as opposed to
|
Ok now you have now two options:
or
You can run both chunks above, |
You're using Basilisk to ensure that a suitable Python environment exists in which reticulate can use a number of Python packages. The problem with Basilisk is that it forces the use of Conda, which downloads binaries. These binaries have been linked with libraries that may or may not have a different ABI than those used on the user's system. For example, when using Voltron with Guix the C library very likely differs from what has been linked with the Conda binaries.
It seems to me that the use of Basilisk is not actually required if the user can guarantee a suitable Python environment. In Guix we could take care of installing the required Python packages.
While Basilisk could still be a required package, perhaps its runtime use could be toggled with a configuration option or an environment variable. Would you be open to a pull request that accomplishes this?
The text was updated successfully, but these errors were encountered: