Article <mailman.66.1724387030.2890.python-list@python.org>

Deutsch English Français Italiano
<mailman.66.1724387030.2890.python-list@python.org>

View for Bookmarking (what is this?)
Look up another Usenet article
Path: ...!2.eu.feeder.erje.net!feeder.erje.net!fu-berlin.de!uni-berlin.de!not-for-mail
From: dn <PythonList@DancesWithMice.info>
Newsgroups: comp.lang.python
Subject: Re: new here
Date: Fri, 23 Aug 2024 16:23:42 +1200
Organization: DWM
Lines: 113
Message-ID: <mailman.66.1724387030.2890.python-list@python.org>
References: <87ikvuzv8g.fsf@rpi3> <liktbqFgjfU2@mid.individual.net>
 <87zfp4bgm3.fsf@nightsong.com> <lipj21Flti1U6@mid.individual.net>
 <6da65aef-86d7-46e7-90cc-692985ffaf29@DancesWithMice.info>
 <mailman.65.1724358976.2890.python-list@python.org>
 <liqeqiFprmmU1@mid.individual.net>
 <3f06d06e-732f-4afa-ba23-24aa1b742de4@DancesWithMice.info>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cancel-Lock: sha1:tw7LuK+ImNIYLiQvy0p2sodF/ok= sha256:GNuFZ75uoNk1SQxVgYP+BfdPD1WktuhSCyosKb5rQbU=
User-Agent: Mozilla Thunderbird
Content-Language: en-US
In-Reply-To: <liqeqiFprmmU1@mid.individual.net>
Precedence: list
Bytes: 10501

On 23/08/24 15:43, rbowman via Python-list wrote:
> On Fri, 23 Aug 2024 08:36:02 +1200, dn wrote:
>> 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'm probably guilty. I mentioned in passing the older protocols like
> finger could even be implemented on something like the Pico W with
> MicroPython.

The question arose because his message doesn't appear either in the 
conversation/email thread 'here', nor on the Archive. Perhaps not sent 
to the list?


> I am confused by the cross-over to Python-list. I only read/post to
> comp.lang.python. Is that echoed to Python-list or vice versa?

As I understand it, posts to 'the list' may be made at comp.lang.python 
or by email. Once on the server, messages are reflected back to both. 
Thus, Thunderbird is not set-up to use the newsgroup and keeps 
complaining at me when it's asked to reply to both. So, all 
contributions (from me) enter the server via email.


>>> 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?
> 
> I've only used CircuitPython on the Adafruit Playground Express.
> https://circuitpython.org/board/circuitplayground_express/
> and MicroPython on the Pico W. Since then Adafruit has expanded their
> collection of boards and support them with CircuitPython.
> 
> One difference that makes them hard to compare is the Express has quite a
> few on-board sensors like the Arduino Nano Sense 33, and interfaces to
> them are baked into CircuitPython.
> 
> The Pico W has a wealth of I/O most doubling as I2C, PWM, or A/D with only
> a onboard LED for the mandatory 'hello world' blink code. MicroPython is
> more generic and you may have to import modules for specific external
> devices like the SSD1306 OLED display. That's easily done with Thonny or
> pipkin.

Adding a display to the Pico-W is my next project... After that, gyros 
(am thinking it may not go so well, on balance... hah!).

The Pico-W impresses. Its built-in Wi-Fi/Bluetooth capability makes life 
a lot easier (inside building use).

Apart from the earlier comment, my biggest frustration has come from the 
lack of facilities in Thonny compared with PyCharm - but will pick-up 
skills there, no doubt.

Conversely, (to having a separate radio-chip) I think I prefer the idea 
of being able to connect the Pico to whichever sensor(s) is/are 
actually-required. However, this is applied use - not learning or 'playing'.


> As far as core Python I'd say they're similar. MicroPython is more generic
> and may require more work to set up where Adafruit can match the boards
> they have developed.
> 
> As I said it's been a while but MicroPython has the _threading module so
> you can utilize both cores of the RP2040. Adafruit's new Feather has a
> RP2040 and like the Pico W assumes you'll be using the PIO to externals
> rather than anything onboard so CircuitPython probably has it.
> 
> https://www.adafruit.com/product/4884
> 
>  From the horse's mouth:
> 
> "There is great C/C++ support, unofficial (but really good) Arduino
> support, an official MicroPython port, and a CircuitPython port! We of
> course recommend CircuitPython because we think it's the easiest way to
> get started and it has support with most of our drivers, displays,
> sensors, and more, supported out of the box so you can follow along with
> our CircuitPython projects and tutorials."

Whilst agreeing with the "easiest way to get started" claim, it probably 
also leads to the assumption that it will (later) be easier to run out 
of capability. Hence, that MicroPython would be the better professional 
option - assuming one already knows Python.

Yes, a degree of 'comparing apples with oranges' - and a 
continually-moving target!

========== REMAINDER OF ARTICLE TRUNCATED ==========