Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distribute bytecode compiled sources #3050

Closed
rth opened this issue Aug 31, 2022 · 1 comment
Closed

Distribute bytecode compiled sources #3050

rth opened this issue Aug 31, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@rth
Copy link
Member

rth commented Aug 31, 2022

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:

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

@rth
Copy link
Member Author

rth commented Apr 24, 2023

Closing as resolved in 0.23.0

@rth rth closed this as completed Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant