On 23/08/24 07:49, rbowman via Python-list wrote:
On Thu, 22 Aug 2024 10:40:52 -0700, Paul Rubin wrote:
The Pico uses MicroPython which is stuck on an old version of Python,
unfortunately.
How did this enter the conversation/thread?
Paul's 'contribution' does not even appear on the Archive...
I think it's up to 3.4 in general and erratic past that. It doesn't have
the match from 3.10. I don't think it has f-strings though it may have
the walrus. There are workarounds but it can be annoying.
Two points:
- it's cut-down to work on bare-metal which makes for low demands on
resources, but commensurate shortage of the facilities we CPython
developers take for-granted (ie may allow ourselves to find annoying)
- it has f-strings, but frustrates those of us who prefer F-strings
- the docs point-out that (compared with full-fat Python) it is less
consistent across environments. Accordingly, worth reading the "Quick
Reference for [your processor]" sections of the docs, eg R-Pi Pico
version only has half of the ADC-methods.
Once scale expectations to take into account the power of the processor,
MicroPython goes-like-the-clappers!
I haven't worked with CircuitPython lately and don't know if it has pulled
in later features.
Have you (gentle reader) used both and feel able to offer a comparison -
when to prefer one over the other?
[https://www.phrases.org.uk/meanings/like-the-clappers.html]
--
Regards,
=dn
--
https://mail.python.org/mailman/listinfo/python-list
