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
As suggested by @tiran in this discuss.python.org bytecode compilation adds significant overhead to the load time, and we should consider distributing .pyc files only.
As discussed in the above-linked thread, if we ship .pyc files only, for pure Python packages, the file name would no longer be *py3-none-any.whl but Python version specific (although platform independent).
re:
You already have a CDN for your binary WASM builds. Maybe you could also provide “binary” wheels for pure Python packages.
@tiran With the current distribution model where there is a single version of a package per Pyodide release, we would rather not add pure Python packages on PyPI as it increases the maintenance burden for us. If users are able to upload packages to this CDN independently one day, that's indeed something worth considering, but this would require significant work in #3049
The text was updated successfully, but these errors were encountered:
As suggested by @tiran in this discuss.python.org bytecode compilation adds significant overhead to the load time, and we should consider distributing .pyc files only.
There are some implications for the tracebacks but if it allows reducing load time, it's a reasonable compromise I think.
As discussed in the above-linked thread, if we ship .pyc files only, for pure Python packages, the file name would no longer be
*py3-none-any.whl
but Python version specific (although platform independent).re:
@tiran With the current distribution model where there is a single version of a package per Pyodide release, we would rather not add pure Python packages on PyPI as it increases the maintenance burden for us. If users are able to upload packages to this CDN independently one day, that's indeed something worth considering, but this would require significant work in #3049
The text was updated successfully, but these errors were encountered: