Juha Jeronen

Sure! I'll add some tests and push them, probably later today.

Done, test added. It gets picked up by ``run_tests.py``, and passes in Python 3.6. While at it, I made the mechanism a bit more user-friendly: since the keyword arg name...

Ping? Anything that still remains to be done?

One thing I've thought about since I posted this is that having seen Racket, what Python is missing is a separation of the concepts of ``require`` (import) and ``provide`` (export)....

Star-imports, exactly, that's what I meant by Python "almost getting it right". The ``__all__`` magic is currently useless except for use with the REPL, whereas it could have been a...

Thanks for the refactor suggestion, it was excellent! It [solved the issue](https://github.com/Technologicat/unpythonic/tree/master/unpythonic/syntax) for me. Thinking back, I suppose the problem was that I was thinking of all code as one...

Hmm, a very pythonic viewpoint. The reason I opened this ticket is that this also came up over email, and @azazel75 said the behavior I described (a block macro requires...

Yes, the ``assert isinstance(new_tree, list)`` is the very last item in the stack trace, but Python has spoiled me to expect the error message to already contain all necessary information....

Update: during my investigation of #21, I noticed that in ``macropy.core.macros.Block.detect_macro``, there is already a special case to automatically wrap a single *expression* returned by a block macro into an...

I agree it's fine to expect a list of statements. Knowing that, there's no problem. I didn't know the ``ast.Expr`` trick is for backward compatibility only, as the code itself...