MicroPython Forum

We do hope to merge 1.13 in at some point after the holidays. (We're crunched on the ESP32-S2 at the moment.)

I'd suggest you reach out to WarriorOfWire about it on that PR or an issue. They've done most of the CP work. Thanks!

CircuitPython runs on Raspberry Pi, via Blinka Seeing recent queries on the Raspberry Pi bulletin board, I'm not convinced this is a great idea. All of Adafruit's device drivers are being moved over to Blinka, so you basically have to install Blinka (and all of its many, many dependencies) in order...

Many thanks for this, much food for thought. The best thing to do is to allocate the memory on the MicroPython heap with a bytearray object and then pass the bytearray into the object that takes it. That way the memory can be used again if you get more data. Do you mean ask the initial library to w...

In CircuitPython we used to convert our RST to pyi but now we have pyi directly. The autoapi extension is useful to generate the docs from the pyi: https://github.com/readthedocs/sphinx-autoapi

1) If the Python script doesn't need to access the individual bytes of the data chunk, can I avoid copying the data into and out of MicroPython's heap? Could I maybe package up the data chunk as a "bytes" object while it is outside of MicroPython's heap, or will this cause complications with the ga...

Typically the MicroPython or CircuitPython device can't do anything to get the Host OS to flush filesystem changes. It's really up to the user on the host OS to "eject" or "safely remove" the device before resetting.

Hi Hugo, take a look at the SAMD port PR: https://github.com/micropython/micropyt ... d539a461fd

The LPC55 is supported by TinyUSB just like the SAMD so that side of things should be similar.

Espressif is planning on using TinyUSB in the ESP-IDF for the -S2 (https://github.com/hathach/tinyusb/pull/282) so adding basic support should be easier in MicroPython (which uses TinyUSB for SAMD and nRF) and CircuitPython (which uses TinyUSB for most ports.)

My guess (haven't used it myself) is that it's an int value that matches the value in the BLE spec. Address types are usually "static public", "random static" (here is a Nordic post about it https://devzone.nordicsemi.com/f/nordic-q-a/2084/gap-address-types), or two others derived from the bonding k...

We recently ran this down in CircuitPython because we wanted native code to have access to the instance rather than just the native struct. (Our PixelBuf class calls `_transmit` on the subclass.) Here is the PR: https://github.com/adafruit/circuitpython/pull/2550 There was definitely work to make th...