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
support application/wasm in mimetypes and http.server #79584
Comments
web browsers have recently gained ability to run webassembly code and for that a new content type has to be add to web servers for optimal use: wasm => Content-Type header : application/wasm spec says it : "Firefox streaming compilation needs Content-Type header set" cf: https://groups.google.com/forum/#!topic/emscripten-discuss/C7-i1gqWay4 google's filament documentation says: it would be logical since simple htt server is mostly used for testing software to offer support of that new techonology. |
Python 3.7 is in feature-freeze, so any new features like this will have to be 3.8 only. |
We don't generally add a mime type until it is a de-jure or de-facto standard. If it is still in testing it is probably too soon to add it. For testing, you can always add it yourself in your code via the api that mimetypes provides. |
Sure, but i was considering the cpython in the browser/webview/electron case where python modules are served as .wasm files, i'm about to do it for my port and pyodide already does. scientific cpython stack in the browser: python repl in the browser experiment: Also i think cpython in the browser could be be already beyond testing and so far provides the best sandboxing configuration available around : |
According to bpo-34758, this was already added to 3.8’s “mimetypes”. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: