On 15. 01. 20 23:59, Zbigniew Jędrzejewski-Szmek wrote:
### Solution 5: Stop shipping mandatory bytecode cache
This solution sounds simple: We do no longer ship the bytecode cache
mandatorily. Technically, we move the `.pyc` files to a subpackage
of `python3-libs` (or three different subpackages
Am 16.01.20 um 21:15 schrieb Zbigniew Jędrzejewski-Szmek:
>> Accommodating component versioning would mean deploying
>>
>> /usr/lib/pythonxx/site-packages/something-semver.zip
>
> This path includes xx, which contains the major and minor numbers. So
> adding "semver" would only allow accommodatin
On Thu, Jan 16, 2020 at 03:36:11PM +0100, Nicolas Mailhot via devel wrote:
> Le 2020-01-16 15:10, Felix Schwarz a écrit :
> >Am 16.01.20 um 13:37 schrieb Nicolas Mailhot via devel:
> >>If we start messing with the Python tree it would be nice to put
> >>each shared
> >>python component in a separat
On Wed, Jan 15, 2020 at 06:05:42PM +0100, Miro Hrončok wrote:
> ### File types (and bytecode caches)
>
> The orthogonal dimension is the file type. Python standard library
> contains directories with both "extension modules" (written in C
> (usually) and compiled to `*.cpython-38-x86_64-linux-gnu.
> Solution 4: ZIP the entire standard library
> (...)
> Nevertheless, this might (in theory) **save 17.8 MiB / 47 %**.
It's my favorite option. Almost 50% smaller is quite good! It would be
very efficient to have such disk space gain!
Using a ZIP file for the stdlib is commonly suggested solution
