Re: [poposal for preparing a pep] sharing package installations between virtualenvs
Joni Orponen <[email protected]>
| Newsgroups | gmane.comp.python.distutils.devel |
|---|---|
| Message-ID | <CA+LW3i3HAhJanJ4jp8q_KrVQXfWKkhhKzNTTgzN7vTwkjB7n8Q@mail.gmail.com> |
On Mon, Oct 8, 2018 at 10:15 AM Thomas Kluyver <[email protected]> wrote: > Have you tried using conda envs? Conda avoids duplication by unpacking all > packages to a shared directory and then hard-linking them into environments. > > I'm not saying that should preclude doing something similar for > virtualenvs, but it's probably worth looking at existing solutions before > embarking on a change of this magnitude. > Buildout has also done this for quite a long time. http://www.buildout.org/en/latest/topics/optimizing.html On Mon, Oct 8, 2018 at 10:22 AM Freddy Rietdijk <[email protected]> wrote: > What Conda and Nix do is basically having a store with packages, and then > indeed linking them to form environments. While this works, it is important > that one is very careful tracing how the packages are built, because not > doing so can easily cause trouble in case of modules with extension types. > Buildout shares this problem. PIL is a classic example of an egg, which can have vastly different runtime based on the compile time. -- Joni Orponen -- Distutils-SIG mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/mm3/archives/list/[email protected]/message/DTM2EGNZ5MQHZN36T4U5HQ2AE4MJRVAO/