stubs package with data_files

[FoamyGuy]

With package_data and packages the installed files end up like:

/[Python]/lib/site-packages/circuitpython-stubs/digitalio
/[Python]/lib/site-packages/circuitpython-stubs/displayio
/[Python]/lib/site-packages/circuitpython-stubs/...

when it is like this the IDE will not recognize the stubs unless they are imported like this:

from circuitpython import digitalio

To fix we can use data_files to install all of the circuitpython stubs into the root of ../site-packages/

This allows the IDE to recognize the stubs when used as normal in circuitpython code i.e.

import digitalio

I tried some other ways of installing multiple packages instead of using data_files but never found a working solution, perhaps there are some though.

I tested the stubs from this technique successfully with PyCharm, but not with this repo specifically. I was able to get local pip install and pip install from a test pypi listing to work correctly.

[tannewt]

Awesome! Thank you! Do we have auto-release set up already?

[FoamyGuy]

I don't think it is currently set up. There is a circuitpython-stubs listing on PyPi so perhaps it was at one point but doesn't seem to be actively running still.

In the libraries there is a workflow in the release.yml actions file that uses twine to upload to pypi. Only glanced through the actions files in this repo but didn't any pypi related actions in them.

Do we want to use essentially the same release action from the libraries? if so I can PR that, or if there is a different way that is needed I'd be happy to give it a try, but may need further direction.

[tannewt]

Do we want to use essentially the same release action from the libraries? if so I can PR that, or if there is a different way that is needed I'd be happy to give it a try, but may need further direction.

Ya, I think so. I think the existing releases were manually done. Following the library approach is a good idea.