python-imphook VS pycopy-lib

Recently, there was a discussion on the python-ideas mailing list about possibility to add "arrow functions" to Python (familiar from modern JavaScript). I made a proof-of-concept implementation using the imphook module, which allows to easily add hooks for module importing, in particular (by not limited) to implement macro-like functionality like that.

For as long as you're a human and belong to category of "people", you can answer that question as good as anyone else. And your answer is ...?

(Just in case my answer is: https://github.com/pfalcon/python-imphook , yet another (but this time unsucky, I swear!) module which allows people to implement macros (among other things)).

And on top of it, and slightly more convenient API is built as a small Python module, again portable between Pycopy and CPython: https://github.com/pfalcon/python-imphook

So, unlike MicroPython itself, which was started by another guy, micropython-lib was started and largely done by me (but initially contributed it to the micropython project, yeah). I continue that work in https://github.com/pfalcon/pycopy-lib

In this version, improvements in native types subclassing support. Pycopy standard library, https://github.com/pfalcon/pycopy-lib, also sees further development and improvements.

Plug pure-Python bytecode (or JIT) compiler: https://github.com/pfalcon/pycopy-lib/tree/master/ucompiler (prototype/WIP)

Plug pure-Python bytecode (or JIT) compiler: https://github.com/pfalcon/pycopy-lib/tree/master/ucompiler (prototype/WIP)

Thanks. Except it's not mine, but CPython2's stdlib module (written by many people) ported to Python3.5. What's mine is Pycopy stdlib ucompiler module: https://github.com/pfalcon/pycopy-lib/tree/master/ucompiler, written by me from scratch based on the experience with CPython2's module (I figured I'd have better time writing one from scratch than cleaning up CPython2's module).