Macros do not make code unmaintainable by their virtue alone any more than pointers, references, or any other language feature.
I suggest you look into code review and use some code checking tools like style checkers, linters, and test coverage report generators.
Hy is essentially a self-evaluating macro that spits out Python AST.
So you can use map, filter, and friends just as easily on Hy code as you can elements in a list or tuple.
In the end you get Python AST. We generate all of the boiler plate instead of writing it out.
You also do "have" macros in a very obtuse way in Python. You have eval, compile, and the ast module. You can write code, in Python, to modify or generate Python code. It's just tedious and cumbersome in a language where the code is not also data.
Using this to write normal code is also a bad idea and a maintenance nightmare. The issue isn't that it is tedious and cumbersome to do so. If it's tedious and cumbersome to make my life hell, that's a feature.
You essentially have macros in Python: they are hard-coded in the form of phrase structure rules in its grammar.
Macros are essentially this: new phrase structure rules in your interpreter/compiler that you program yourself and stick into your application.
What you're really saying is actually that you don't need any new macros beyond the phrases which the benevolent dictator for life has bestowed upon you in the parser.
Whenever a programmer upgrades to a newer Python which has new syntactic transformations in its updated grammar, and then uses these new things, that programmer contradicts his or her earlier claims that no new macros were needed.