On Mon, Oct 8, 2018 at 12:10 PM Ronny Pfannschmidt
wrote:
> Hi Joni,
>
> thanks for the references.
>
> buildout has been on my inspirations for this proposal.
>
> The historic shift of buildout vs virtualenv+pip as well as build-outs
> unfortunate dependency on eggs are some of the pain points
Hi Freddy, Thomas
thanks for the well cautioned notes.
I'm vaguely aware that both, nix and conda, as "meta package managers"
have a effective way of linking correct sets of packages including the
tracing.
however both tools never made it into a consistent set of tools that my
peers, coworkers,
On Mon, Oct 8, 2018 at 10:15 AM Thomas Kluyver 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
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.
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
