On 31 October 2017 at 22:13, Leonardo Rochael Almeida
wrote:
>
> Those are issues that buildout has solved long before pip was even around,
> but they rely on sys.path expansion that Ronny found objectionable due to
> performance issues.
>
The combination of network drives
Hi,
On 31 October 2017 at 05:22, Nick Coghlan wrote:
> On 31 October 2017 at 05:16, RonnyPfannschmidt <
> opensou...@ronnypfannschmidt.de> wrote:
>
>> Hi everyone,
>>
>> since a while now various details of installing python packages in
>> virtualenvs caused me grief
>>
>>
On 31 October 2017 at 05:16, RonnyPfannschmidt <
opensou...@ronnypfannschmidt.de> wrote:
> Hi everyone,
>
> since a while now various details of installing python packages in
> virtualenvs caused me grief
>
> a) typically each tox folder in a project is massive, and has a lot of
> duplicate
I would like to explicitly avoid Hardlink Farms
because those still have "Logical" duplication
i'd like to bind in the new paths without having it look like each
virtualenv is 400-1000 mb of distinct data
-- Ronny
Am Montag, den 30.10.2017, 22:23 + schrieb Thomas Kluyver:
> On Mon, Oct 30,
, the behaviour i aim for would be moslty like
virtualenv but without the file duplication.
For what it’s worth, conda environments use hard links where possible, so
limiting duplication...
Maybe conda would solve your problem...
-CHB
I beleive nix could also benefit from parts of such
On Mon, Oct 30, 2017, at 07:16 PM, RonnyPfannschmidt wrote:
> in order to elevate those issues i would like to propose a new
> installation layout,
> where instead of storing each distribution in every python all
> distributions would share a storage, and each individual environment
> would only
Hi Freddy,
im well aware what nix currently does for python packages and suffered
my fair share from it.
What i want to do is simply store those wheels that pip would first
generate and unpack into each environment into a location where each
environment shares the unpacked files more directly
Hi Ronny,
What you describe here is, as you know, basically what the Nix package
manager does. You could create something similar specifically for Python,
like e.g. `ied` is for Node [2], or Spack, which is written in Python. But
then how are you going to deal with other system libraries, and
Hi everyone,
since a while now various details of installing python packages in
virtualenvs caused me grief
a) typically each tox folder in a project is massive, and has a lot of
duplicate files, recreating them, managing and iterating them takes
quite a while
b) for nicely separated