-
Notifications
You must be signed in to change notification settings - Fork 5
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
Update packaging URLs, etc? #11
Comments
Thanks for the suggestion @bollwyvl! I'll update the metadata soon.
Yes, I'll start migrating the docs soon. I think we won't need
Sounds good. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Good to see this getting shipped and tagged independently.
Some thoughts on packaging while mucking with conda-forge/pyodide-build-feedstock#15:
Home
,Bug Tracker
(and addSource
) metadata inpyproject.toml
?sphinx-js
?On the topic of metadata, and maybe belonging in some other repo: irrespective of how pyodide/emscripted wheels on PyPI might go, it might well be time to consider getting a
Framework :: Pyodide
classifier, or having an initial go at a deeper taxonomy which might include a way for packages to signal they are functional/tested (with or without limitations) in pyodide.The text was updated successfully, but these errors were encountered: