Can we make it clearer how people making accessories should support them in MicroPython?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, python
- Domain
- developer-experience, documentation
Research direction
The issue names no files, tests, or entry points. Start by reviewing the current single-file MicroPython workflow and the example-code approach described here; done means an agreed recommendation for accessory authors and a decided direction for future support.
Written by the indexing model from the issue text.
Description
...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
-
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?
-
What can/should we do in the future to improve this?
- Dominant language
- JavaScript
- Stars
- 201
- Forks
- 126
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bbcmicrobit/PythonEditor
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
bbcmicrobit/PythonEditor#406 ·
-
U Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
bbcmicrobit/PythonEditor#405 ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
bbcmicrobit/PythonEditor#391 · 2 comments · 6 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
bbcmicrobit/PythonEditor#375 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
bbcmicrobit/PythonEditor#367 ·
All issues in bbcmicrobit/PythonEditor
Similar issues
-
bug customer-eng Durable Agents Inngest status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-cao#13475 ·
-
[BUG]: "Clear All" in Settings doesn't clear the saved analysis, old data comes back after reload Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
AOSSIE-Org/OrgExplorer#253 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
oxc-project/oxc#26944 ·
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100