Live data from Hacker News

CircuitPython: Programming Hardware in Python

github.com

11–20 of 87 posts

Re: CircuitPython: Programming Hardware in Python

#11
post #7
post #5

Earlier quoted context omitted.

I read the readme differences, but any obvious benefits to one or the other?

Core modules are a bit better laid out, meaning you will have a more unified experience across different dev boards. Additionally, there are more boards that appear to be supported, but don't quote me on it. Things like os/time/filesystem stuff act how you would expect running cython. IIRC the big selling point is anything that you can run on CircuitPython you can run in cython, whereas with MicroPython some of the O…

Point of clarification: By Cython do you mean Cython or CPython?

Re: CircuitPython: Programming Hardware in Python

#14
post #9

I've used CircuitPython for one production hardware project which is in the wild. Safe to say that the increased draw on the included battery and higher memory usage weren't a concern here, but they are both significant. Developer productivity is through the roof though. I'd say the biggest pain points for me (unless I'm missing something/they've added more stuff recently) were created by the lack of support for what…

Out of curiosity, what about this particular project made you opt for CircuitPython? Was it something targeting hobbyists and wanting to allow them to tinker with it? I'm not trying to put it down because I like CircuitPython, but I would not even consider it for a general production device.

Re: CircuitPython: Programming Hardware in Python

#15
That’s a very misleading headline. I got the impression this was something akin to VHDL or Verilog or SystemC in python. “Programming Hardware” the way it’s used here is pretty much the same as vanilla python, though I suppose a lot in this industry constantly need reminding of that.

Re: CircuitPython: Programming Hardware in Python

#18
post #5

Earlier quoted context omitted.

It has 7,000 more commits than MicroPython, to say it is a rebrand is unfair.

I read the readme differences, but any obvious benefits to one or the other?

I was just having a chat w/ a contributor yesterday and he told me a large aim of Circuit Python over MicroPython is to make the code you are writing in Circuit Python more transportable.

I.e. You write code in circuit python, and that same code will run on a little micro, and also a full blown Raspberry Pi.

This is apparently done at the expense of some prettiness.

Re: CircuitPython: Programming Hardware in Python

#19

That’s a very misleading headline. I got the impression this was something akin to VHDL or Verilog or SystemC in python. “Programming Hardware” the way it’s used here is pretty much the same as vanilla python, though I suppose a lot in this industry constantly need reminding of that.

There's MyHDL. Turns Python into a hardware description and verification language:

https://github.com/myhdl/myhdl

Re: CircuitPython: Programming Hardware in Python

#20
post #17

What adafruit board would be best for a beginner (at circuit python but long time developer otherwise) dad and his 8 year old kid?

from a programming point of view, all are the same. But if you want to introduce your kid to play with sensors and other stuff, I'd get Playground Blefruit[1]

[1]: https://www.adafruit.com/product/4333

Post reply on HN