-
-
Notifications
You must be signed in to change notification settings - Fork 517
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
Describe usage of pyscript editor #7017
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7017 +/- ##
=======================================
Coverage 82.24% 82.25%
=======================================
Files 331 331
Lines 49420 49420
=======================================
+ Hits 40647 40649 +2
+ Misses 8773 8771 -2 ☔ View full report in Codecov by Sentry. |
Looks great! 2 suggestions: -Maybe introduce some paragraph spacing ( empty lines) in text blocks. For example, the text block at the top is quite long. Without spacing the text becomes monolithic and harder to follow. This is true when viewed in desktop version, but especially in mobile. -Regarding the below: maybe provide a short explanation and / or a link to a a way / tools to check if libraries have been compiled for Pyodide, or are available as pure-Python wheels from PyPI? ...that the libraries have been compiled for Pyodide or are available as pure-Python wheels from PyPI. So something like: -To check if a compiled version is available, visit the Pyodide packages list to see the libraries that have been compiled for Pyodide. This list includes packages that can be loaded with To check if a wheel is available, look for a .whl file in the files section of the lbrary on pypi.org, or run the following command:
|
This updates to pyodide 0.26.1 and adds a description of the usage of the pyscript editor. Starts from #7016.
I took the opportunity to make the guides a bit more
how-to
like to align with Diataxis.Todo: