-
Notifications
You must be signed in to change notification settings - Fork 9
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
Handling shared libraries #2
Comments
OK so the basic strategy is that shared libraries go into
All of them. Name clashes are avoided because very few things go into
The same as with conda, so very few + all of the CDTs
Yeah, this is a fun one. So I believe that the easiest thing to do is to have a separate copy of Python (obtained via the Python wheel) within |
Really interesting idea! 💡
If this experiment proves successful, it would be interesting if CPython could add support at startup for loading libraries, by default, from |
Ultimately, That'd be great! |
It does not seem to be a correct approach to the issue, especially for packages that link with How about making use of |
Am still learning how this tool works. So am not sure what it is already done to address this issue. Namely how do shared libraries (outside of the Python package) get handled? Alternatively if these are open questions, how should they be handled?
The text was updated successfully, but these errors were encountered: