Re:How we rolled out one of the largest Python 3 migrations
by weberc2 on Wednesday September 26, 2018 @06:26PM
(#18080767)
Fair point. Our largest Python image has only 255 Mb of Python dependencies and ~50 Mb of source code. If we could use alpine (our compliance auditors strongly prefer centos base images), it would only be ~400 Mb. This is easily an order of magnitude bigger than an equivalent Go program, but still quite a lot better.
[ Parent
| on HN ]
Re:How we rolled out one of the largest Python 3 migrations
by icebraining on Wednesday September 26, 2018 @08:34PM
(#18081376)
Is that really just Python code?? Must be over a million lines, no? I've worked with Odoo, which is a bit of a kitchen-sink (ERP, CRM, POS, sales, accounting, invoice, stock management, manufacturing control, website builder, marketing and a bunch more) and its Python code weighs just 15MB, the rest is JavaScript or data files.
Re:How we rolled out one of the largest Python 3 migrations
by weberc2 on Thursday September 27, 2018 @11:34AM
(#18085465)
It's not just souce code--it's also docs and test code and other things that are tedious to omit given our current Docker image hierarchy and repository structure. Our docs are largely Sphinx docs in Python docstrings; a decent minifier could probably reduce this, but it's probably not worthwhile for a ~5% improvement on overall image size.