pycopy VS picoweb

Oh, so you're interested to get 100 tomes of technical drawings for SpaceX? You may be out of luck with it, but with any open-source project you're in luck - source to answer all of your questions is right there ;-). https://github.com/pfalcon/pycopy in this case. There's also the testsuite which formally specifies everything Pycopy can do (coverage 97%): https://github.com/pfalcon/pycopy/tree/master/tests . Finally, the docs include the section on specific differences with CPython3.4: https://pycopy.readthedocs.io/en/latest/differences/index.html (but that's human-written, so definitely not complete). By the way, docs are 381 pages rendered as a PDF: https://pycopy.readthedocs.io/_/downloads/en/latest/pdf/ .

Really? Here's direct link to the closest subsection header: https://github.com/pfalcon/pycopy/#the-unix-version , and quoting it here for you:

Well, here it is: https://github.com/pfalcon/pycopy/blob/master/py/vm.c#L367

https://github.com/pfalcon/pycopy/tree/v3.5.0 (if you prefer to drop people into the code, since the release URL does not contain release notes)

Checkout micropython and install the picoweb package. It can do almost all of the stuff flask is capable of Github Picoweb

No. It has its own web micro-framework: https://github.com/pfalcon/picoweb . As you may imagine, it's minimalist (literally, pico-framework) and runs even on microcontrollers.