-
-
Notifications
You must be signed in to change notification settings - Fork 106
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
A slimmer python #581
Comments
I rencently have been pondering something similar when I noticed that the conda-forge Python interpreter is about 50MB larger than the Let me know if this is a duplicate question: #586 |
Yeah it sounds like the same thing. Let's consolidate into this issue. If you spot anything else that hasn't already been suggested for splitting above, please feel free to add that as a comment here. Thanks! 🙏 |
From Duplicate: #586 Comment:Would it be of interest to provide a I noticed that the python3.10 lib directories differ about 50MB in size:
The conda-forge |
Do |
about 0.5MB and 1.2MB respectively it seems. |
IMHO No strong feelings on |
Comment:
I'm wondering if there is enough enthusiasm for having a slim python build. My main motivation is to help ensure that downstream packages that depend on python, also declare the dependencies they have on other libraries. The ones that come to mind are:
I'm not sure about the implementation, but maybe we can have a behavior similar to pip, where during the build process they aren't pulled in automatically, but for regular users they are? I know that the pip feature is engrained pretty deep into conda, so maybe it isn't that desirable to use it, but the behavior:
python-readline
,python-sqlite
,python-tk
as part of their dependencies.With non-python packages, this has typically resulted in the creation of a "core" package. This would mean that the dependency graph might look like
The text was updated successfully, but these errors were encountered: