Juha Jeronen

Yes, sounds reasonable. Let's change this in the next version. (Sorry I missed this earlier - I've been away from `mcpyrate` for a while.)

As of 9bf1461 (release 3.3.0 and later), `runtests.py` runs both tests and demos. As of 42d93d4 (release 3.2.0 and later), `macropython -c .` clears `.pyc` caches in the current directory....

Fixed in 3.6.1, now available on PyPI. Thanks!

Now that we have a proper CI process (see #5), what remains is to bump up the test coverage significantly. Issue title changed.

As of [`unpythonic`](https://github.com/Technologicat/unpythonic) v0.15.0, there is an experiment with a very rudimentary macro invocation destructuring system in [`unpythonic.syntax.nameutil`](https://github.com/Technologicat/unpythonic/blob/master/unpythonic/syntax/nameutil.py). This functionality was needed by some of the macros, and being experimental...

Same in `unpythonic`; tracked in https://github.com/Technologicat/unpythonic/issues/83

As of v3.6.2, we fill in the `end_lineno` and `end_col_offset` info in the global postprocess pass (copying it from reference nodes), but that's literally the only thing we do with...

Hmm, the check in https://github.com/azazel75/macropy/blob/master/macropy/core/cleanup.py#L63... Shouldn't we have `bytes` and `complex` there, too?

Hmm, talking to myself here, arguably point 6 is the same thing as boilerplate shaving (point 1), though to quote my own code as an example, the boilerplate may get...

Hmm, strictly speaking, point 3 is a subset of point 2, since the transpiler needs access to the source code, or an AST, of the code to be sent (like...