MicroPython Forum (Archive)

Thank you for all of your hard work.

I am going to fork to Pycopy.

v/r
Jeff

Is there a place to download pre-compiled pycopy binaries for the esp32 like there is for micropython?

I am having a hard time getting that toolchain to compile micropython setup which is distracting me from the core of my project.

At the end of the day I just wanted to use picoweb... I don't really care about the distro-war of micropython vs pycopy.

If you choose to setup your own distro/community ... would it not be nice to find a name which actually makes you feel good about it? That tells something about your distro usp? Like Adafruit did with CiruitPython. They also copied the MicroPython project (hence, they also could have chosen PyCopy), but the name CircuitPython made it clear they are focusing on 'circuits' ...

Your vision is more a combination of 'Minimal', 'AnyWhere' and 'Python', right?
Some suggestions ... (Free of charge!)? ... MiniPython, NanoPython, PicoPython, UniPython.

shyft wrote: ↑

Wed Mar 27, 2019 1:33 pm

Is there a place to download pre-compiled pycopy binaries for the esp32 like there is for micropython?

I don't really care about the distro-war of micropython vs pycopy.

No.

I have to admit, I was thinking about this.

But:

• MicroPython (including my fork) is an OpenSource project, giving its users the right to use (and modify, if they like) the sources. As any other right, it needs to be exercised. Further evolution of OpenSource project actually depends on people playing with source. In this regard, target audience of my project is definitely people who are interested to work with the source (or learn doing that).
• I'm not interested in any "distro wars" myself either. But a reason why I would put up binaries releases would be that I want to "compete" for attention of people who are interested in just binary downloads (vs development of OpenSource project). Well, that's not what I'm interested in, at least not now. What I'm interested in is to finish implementation of the features which were started in the mainline, which I can't finish there now, and thus doing in my fork instead. When that work will be finished, we'll see what will be next steps.

So, summing up: I'm thinking about it. But what I'm doing now in my fork are things I've been thinking about last 3-4 years. When they will be implemented, it will be possible to look into implementing things which are under thinking now.

shyft wrote: ↑

Wed Mar 27, 2019 1:33 pm

At the end of the day I just wanted to use picoweb... I don't really care about the distro-war of micropython vs pycopy.

picoweb can be persuaded to run with a standard firmware binary. I have run example_webapp.py on a Pyboard D SF6W by doing the following:

• Acquire example_webapp.py and squares.tpl from PyPi
• Edit example_webapp.py to replace ulogging with logging and to set
  IP and port
• Using upip install picoweb, utemplate
• Edit /flash/picoweb/__init__.py to replace ulogging with logging
• mkdir /flash/picoweb/templates
• cp squares.tpl /flash/picoweb/templates/
• cp example_webapp.py /flash/picoweb/

The latest Pycopy contains changes required for uasyncio 3.0: viewtopic.php?f=15&t=5699#p33792 .