You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While taking on some "good first issues" the typing issues always seem to popup. Wthout a good prior knowledge of Python types and custom Circuit Python types such as i2c: busio.I2C it's actually much harder than expected. A place that lists most if not all the different types that can be used and examples of their syntax usage would be greatly appreciated. Having that live inside the typing repo as an example or multiple examples seems the most logical place.
Tekktrik suggested making this an issue and volunteered as tribute to do it.
The text was updated successfully, but these errors were encountered:
You can use the words type and class interchangeably. As such, a list of all of them would not be trivial to gather and keep up to date. And, in my opinion, would not be useful (too many stuff, no good way of finding relevant bits)
As per the syntax, typing in CircuitPython is (at least broadly) the same as doing it in any other Python implementation, every resource in the web about the topic should help getting a grasp of it.
Also, I expect most of the libraries to be using foo: class, foo: Optional[class] and perhaps some foo: Union[class_a, class_b] variables... If my assumption holds true, i'd recommend striking any library you want and learn as you go, as it wouldn't be too hard of a task.
While taking on some "good first issues" the typing issues always seem to popup. Wthout a good prior knowledge of Python types and custom Circuit Python types such as
i2c: busio.I2C
it's actually much harder than expected. A place that lists most if not all the different types that can be used and examples of their syntax usage would be greatly appreciated. Having that live inside the typing repo as an example or multiple examples seems the most logical place.Tekktrik suggested making this an issue and volunteered as tribute to do it.
The text was updated successfully, but these errors were encountered: