Welcome (Please read before posting)

[jimmo]

Welcome to the MicroPython forum, hosted on GitHub Discussions! 🐍

👋 Getting started

Here are some useful tips:

• Anyone can post and reply to discussions, you just need a GitHub account.
• Please search before posting new issues.
• You can use GitHub Flavoured Markdown to format your posts. In particular use ```py ... ``` around your code snippets to get syntax highlighting, see the section below.
• When describing a problem please include information about which version of MicroPython, where you downloaded the firmware from, and which hardware/board you're using. If there's wiring involved, please include a photo.
• When asking your question, please describe what you've already tried. Include code snippets where possible!
• When posting command output, please also include the command that you ran.
• Please do not post answers generated using LLM tools like ChatGPT. Their knowledge of MicroPython (as distinct to Python) is fairly limited and the answers tend to be misleading.
• If you have found a bug in MicroPython or wish to raise a feature request, please use the Issue Tracker, but feel free to raise a discussion here first.

There's also a huge wealth of knowledge at the previous MicroPython forum.

🪣 Categories

If you have a question, please use one of the "Ports" or "Q&A" categories (depending on whether your question is specific to a particular port/board or more generally about MicroPython). For more open-ended discussion see the "General" and "Ideas" categories. We'd also love to hear about your projects too, see the "Show and tell" category.

If you're not sure if something is a bug, it's fine to create a post here. The moderators can transfer the post into an issue if necessary.

⚙️ Code formatting

GitHub Flavoured Markdown uses two different ways to format code.

The first is print("inline formatting") which is where a code snippet is inline in a paragraph. This uses a single backtick around the code -- e.g. `print("inline formatting")`. This is useful for very short expressions and referencing variable/function names.

For blocks of code, use triple backticks with an optional language specifier. For example

```py
while True:
  pin.toggle()
  await asyncio.sleep_ms(100)
```

which will produce the following:

while True:
  pin.toggle()
  await asyncio.sleep_ms(100)

In almost all cases, if you write your code (or paste it in from your editor), select it, then click the <> button in the toolbar (or press Ctrl-E), then the GitHub editor will insert the right number of backticks for you.

📬 Mail filtering

If you are subscribed to the micropython repo and would like to filter discussions separately from issues and PRs, you can match on the message-id which will contain "micropython/micropython/repo-discussions".

For example in GMail, the following two filters will put Issues & PRs into one label, and Discussions in another. Use the "Includes the words" box to enter the query:

listid:micropython.micropython.github.com -"micropython/micropython/repo-discussions"
    ➡️ Archive, Label: micropython
listid:micropython.micropython.github.com "micropython/micropython/repo-discussions"
    ➡️ Archive, Label: micropython/discussions

❤️ Community Guidelines

Please see the MicroPython Code of Conduct as well as the GitHub Community Guidelines.