Contributing MicroPython type stubs for Pyscript #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I created these stubs for the micropython-stub project,
but I think they are better at home in the pyscript org.
The stubs have been created using a combination of scripting, manual edits and and integration of snippets of documentation from the pyscript docs.
for the micropython version the docs are orginised in a parsable manner - I have not found the time to even attempt the same for pyscript as the documentation structure is significantly different.
Possibly the documentation or API reference could be created from the stubs, and integrated into the documentation. But that is a wider discussion.
Structure
@gregersn
As the incoming stubs or overlapping with, and I think more complete than the pre-existing stubs, I have moved them into a subfolder, as they may still be relevant to Pyscript + Cpython use.
what is your recommendation on this ?
Happy to adjust as needed.
Licensing
I publish all my stubs under the MIT License, but have no object to dual licensing under MIT and Apache