The https://github.com/adafruit/Adafruit_CircuitPython_asyncio library is a package of multiple library files, but its package folder does not start with adafruit_: it is simply asyncio. Because the package folders are filtered to match the --package-folder-prefix argument, which defaults to adafruit_, asyncio is not included in the adafruit bundle, though it should be.
I could special-case it, and maybe that's the short-term solution. But what is the reason for the existence of --package_folder_prefix (which can be a list of multiple prefixes, separated by , ). Is it just to identify the package folder easily? Would it be better just to skip the directories that we know are not package folders, such as docs and examples? There should then be only one leftover directory, which is the package folder, if there is a package.
#61 is related, as is this comment by @tannewt that we should use an ignore list instead of an accept list.
The https://github.com/adafruit/Adafruit_CircuitPython_asyncio library is a package of multiple library files, but its package folder does not start with
adafruit_: it is simplyasyncio. Because the package folders are filtered to match the--package-folder-prefixargument, which defaults toadafruit_,asynciois not included in the adafruit bundle, though it should be.I could special-case it, and maybe that's the short-term solution. But what is the reason for the existence of
--package_folder_prefix(which can be a list of multiple prefixes, separated by,). Is it just to identify the package folder easily? Would it be better just to skip the directories that we know are not package folders, such asdocsandexamples? There should then be only one leftover directory, which is the package folder, if there is a package.#61 is related, as is this comment by @tannewt that we should use an ignore list instead of an accept list.