Log file Viewer

[14:18:56] <apollo13> dstufft: around?

[14:19:42] <dstufft> apollo13: hey

[14:20:06] <apollo13> dstufft: so… you do know I am lazy right ;)

[14:20:14] <apollo13> /home/florian/.cache/pip/wheels/a5/03/dd/9e6d815b2ea8ff7b9f84267173539a04c6faee8b0e6b8958e4

[14:20:19] <apollo13> why so many subdirs?

[14:20:24] <apollo13> and what is the last hash

[14:22:59] <dstufft> apollo13: some file systems have a limit on how many sub directories inside of a directory, so the subdirs are to distribute the cache amongst many directories to get around common limits

[14:23:31] <apollo13> but the last one seems kinda redundant if there is only one file in it?

[14:24:11] <dstufft> there might be more than one file in it

[14:24:27] <dstufft> the hash is derrives from the link of the sdist

[14:24:51] <apollo13> ah so building for different py versions would give more than one file?

[14:24:59] <dstufft> yes

[14:25:04] <apollo13> thanks :)

[14:39:26] <ronny> dstufft: btw, any oppinion on more tightly integrating devpi and pip

[14:39:49] <dstufft> depends on what you mean by more tightly integrating them

[14:40:38] <ronny> dstufft: sharing caches locally, and having some way to upload and share wheels/precompiled wheels within a company

[14:42:10] <ronny> (currently using devpi means storing all packages in use twice or trice, once in devpi, once in pip cache, and sometimes once in pip cache from other locations

[15:45:42] <pjdelport> ronny: A quick hack presents itself: maybe just have a tool to hardlink identical files together, and run it over all three caches?

[20:42:33] <ronny> pjdelport: not really interesting