Working on this in #6085, so making this draft for now.

For #6085 at least, it looks like the circuitpython_typing package needs a py.typed file, and setup.py-stubs needs an item entry["circuitpython_typing"] = ["py.typed"] in the build_package_data function.

I've also noticed in tools/extract_pyi.py that there's a set CPY_TYPING with names that were in the old circuitpython_typing.cpi file, that seems to be used to compose an import of (just) those names from circuitpython_typing, around line 246. (And ByteStream isn't in that set.)

(I hope this is useful -- I'm using this issue to get familiar with the code base and build stuff.)

For #6085 at least, it looks like the circuitpython_typing package needs a py.typed file, and setup.py-stubs needs an item entry["circuitpython_typing"] = ["py.typed"] in the build_package_data function.

Thanks, yes, I did some research on this earlier this morning, came to the same conclusion as you, and am testing exactly this locally. I also am conditionally adding some definitions that were in shared-bindings/circuitpython_typing to the library.

Whether circuitpython_typing should be .pyi or .py files is also a bit confusing. In Python 3.10, evaluation of annotations is deferred, which would help. This feature is not in MicroPython yet.

This is the kind of thing we might discuss in "In the Weeds" in a Monday meeting, or at least in discord chat at some point.

Superseded by additional changes to #6085.