MicroPython Forum (Archive)

Let me know how it goes. If it works I mention it in docs.

Since I am big believer in reuseable code I just updated this driver to use unified sensor properties and units as described by CircuitPython design guide. TL;DR default unit is m/s^2 instead of g and values are accessed via sensor.acceleration property instead of sensor.acceleration() method.

I wrote instructions on flashing M5Stack few days ago. TL;DR try erasing flash first and lower baud rate. $ esptool.py --port /dev/cu.SLAB_USBtoUART --baud 115200 --after no_reset erase_flash $ esptool.py --port /dev/cu.SLAB_USBtoUART --baud 115200 write_flash --flash_mode dio --flash_freq 80m --fla...

GPL is viral. If a permissive licensed (MIT) project includes restrictive licensed (GPL) code the GPL license says if the derivative work (in this case Loboris fork) is distributed (for example via GitHub) the whole derivative work must be relicensed as GPL. You cannot have parts of the code under M...

Paul's behaviour online reached a point towards the end of 2017 where, regretfully, I felt that he was doing more harm than good to the project. If you are interested you can read for example this post: https://mail.python.org/pipermail/python-dev/2017-November/150383.html Read through the November...

My only issue of pfalcon/micropython-lib being the official standard library repo would be if it depends on non-official fork of MicroPython. It would be too confusing. If it is usable with vanilla MicroPython everything is fine. Maybe release those packages needing special version of MicroPython as...

Looks awesome! Which license does the code use?

FWIW to me micropython/micropython-lib is the standard lib. Would be nice to get confirmation about which one is used for libraries installed from pypi.

make forks instead of sending PRs That is not very accurate, it's not one or the other, they go hand in hand. You create a fork with the intent of being able to submit PRs, that's how github works best. If that PR is merged you sync your fork with the upstream again. I do understand how Git works. ...

If this is a case of core developers not getting along anymore then yeah that happens. Best thing would be to fix whatever disagreement there is. If not possible then at least make a clear distinction between the projects. Since docs suggest pfalcon/micropython is also called pycopy standard library...