You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem: I use install mypy in docker images so the distribution includes full testing capabilities. When I install from pypi, I get complete mypy with mypyc in my x86_64 docker image (based on python-slim / debian based images)
For mypy-0.820+dev the wheel for CPython 3.8 is currently about 29MB, and uncompressed about 109MB in Linux x86_64.
Adding the -g0 compile flag (excluding debug info from binaries) in build.py, the wheel size is reduced to 11MB and uncompressed to 37MB.
So it would be cool to have a debug flag or anything to control an optional -g0 compiler flag (or the corresponding Darwin / Windows CFLAGS).
Thanks.
The text was updated successfully, but these errors were encountered:
As far as I can tell, while the mypycify entrypoint now supports a debug_level keyword argument, mypy's wheel build set up doesn't override the default of 1. Probably worth doing that? cc @hauntsaninja
Thanks for this great piece of software!
The problem: I use install mypy in docker images so the distribution includes full testing capabilities. When I install from pypi, I get complete mypy with mypyc in my x86_64 docker image (based on python-slim / debian based images)
For mypy-0.820+dev the wheel for CPython 3.8 is currently about 29MB, and uncompressed about 109MB in Linux x86_64.
Adding the -g0 compile flag (excluding debug info from binaries) in build.py, the wheel size is reduced to 11MB and uncompressed to 37MB.
So it would be cool to have a debug flag or anything to control an optional -g0 compiler flag (or the corresponding Darwin / Windows CFLAGS).
Thanks.
The text was updated successfully, but these errors were encountered: