Can we make it clearer how people making accessories should support them in MicroPython?

...using GitHub here, but please @ntoll redirect me if you'd like this in a different forum. Ultimately aiming for visible/public enough

One of the questions we (at micro:bit Foundation) get a lot in relation to the Python Editor and MicroPython in general is "How can I make a library to support my accessory?". At the moment, people tend to publish example code (hex files) and go from there.

Our current 'single file' model makes it hard to do much else, as far as I can see.

So I think there are two questions
1) Given the current state of play, what's the best advice for someone wanting to write python code to support an accessory with micro:bit - IE what should we ask them to provide for MicroPython?

2) What can/should we do in the future to improve this?

L’issue ne nomme aucun fichier, test ou point d’entrée. Commencez par examiner le workflow MicroPython actuel à fichier unique et l’approche du code d’exemple décrite ici ; le travail sera considéré comme terminé lorsqu’une recommandation approuvée pour les auteurs d’accessoires et une orientation décidée pour la prise en charge future seront disponibles.

Rédigé par le modèle d'indexation à partir du texte de l'issue.