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?

此 issue 未指定檔案、測試或進入點。首先檢視目前的單檔案 MicroPython 工作流程，以及此處描述的範例程式碼作法；完成的標準是：為配件作者形成一致同意的建議，並決定未來支援的方向。

由索引模型根據 Issue 內容生成。