[Tooling] Initial implementation of stub checker#884
Draft
elpekenin wants to merge 2 commits intoadafruit:mainfrom
Draft
[Tooling] Initial implementation of stub checker#884elpekenin wants to merge 2 commits intoadafruit:mainfrom
elpekenin wants to merge 2 commits intoadafruit:mainfrom
Conversation
Author
|
Some more info in #881 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As per title, just wrote a minimal (and very subject to improvements) script that will compare the actual implementation (
.py) against the circuitpython-generated stubs (.pyi)Note:
BLINKA_OS_AGNOSTICtargetBLINKA_FORCECHIPenvironment variableThe motivation for this is to find inconsistencies and fix them, such that code is actually portable between devices and not
almost portable because a function signature differs or whatever