The current size limits of 3MB (free plan) or 10MB (paid plan) for the gzipped size are too tight for Python apps because many popular Python libraries contain large binaries.
For example, when I tried to deploy an app using the following libraries, it easily hit the limit (sizes are the sums of the gzipped files of each vendored package):
pandas 2.3.3: 4.22MBnumpy 2.2.5: 2.90MBPillow 11.3.0 (PIL): 0.99MBaltair 6.0.0: 0.74MBlibcrypto.so: 0.62MB
All of them were vendored from the Pyodide v0.29.3 distribution (Python 3.13), synced with workers-py 1.15.0 and deployed with wrangler 4.110.0.
I believe these libraries are very commonly used in the Python ecosystem and cannot be omitted when developing meaningful applications in certain domains.
I believe this is one of the biggest differences from the JavaScript ecosystem.
It would be great if
- the size limit were relaxed for Python Workers,
- such prepackaged/common libraries were excluded from the size calculation,
- or some other solution were provided.
Thank you.
The current size limits of 3MB (free plan) or 10MB (paid plan) for the gzipped size are too tight for Python apps because many popular Python libraries contain large binaries.
For example, when I tried to deploy an app using the following libraries, it easily hit the limit (sizes are the sums of the gzipped files of each vendored package):
pandas2.3.3: 4.22MBnumpy2.2.5: 2.90MBPillow11.3.0 (PIL): 0.99MBaltair6.0.0: 0.74MBlibcrypto.so: 0.62MBAll of them were vendored from the Pyodide v0.29.3 distribution (Python 3.13), synced with
workers-py1.15.0 and deployed withwrangler4.110.0.I believe these libraries are very commonly used in the Python ecosystem and cannot be omitted when developing meaningful applications in certain domains.
I believe this is one of the biggest differences from the JavaScript ecosystem.
It would be great if
Thank you.