(see also previous message in that thread)If Micro Python could run Django, even in some heavily stripped down form, then that would get people's attention. Imagine nginx + uPy
I'm still not sure if Damien was joking regarding Django . And that's definitely not how I intended to use MicroPython myself - while I care primarily about unix port, my original interest is to write unbloated code mostly from scratch. But I picked up Damien's call by following reasons: 1) if we implement Python, it should be able to run existing Python code; 2) specifically, making Python3 standard lib and testsuite would be important milestones.
So, I took Bottle and started to look into what it would take to make it run. That immediately recursed into stdlib, into things like http.server & http.client, whose dependencies I traced down to "leaf" modules like "copy". It took around 5 patches to uPy core to get "copy" to run. Exhausting. In 3 days, I was ready to make this post with conclusion: unrealistic to achieve in short time, long term goal. Well, instead of writing this post, I backlogged it, and wrote another patch.
So, while initially highly unrewarding, following this path uncovers many issues in uPy, and thus very good way to improve it. It's also grounded way to do so, rather than based on own speculations on what should be implemented and what not (if Python3 stdlib requires it, then well, we'll need to implement to be able to claim we're compliant Python implementation).
So, I finally open this thread to get together people interested to run existing apps on uPy, and to share experiencing trying to do so.