Secondly, you can do that with Path.read_text() and pass it to SQLalchemy-core if a query is so complex you want to (although you would lose many other architectural benefits by doing so, it is sometime necessary).

But writing your entire program like that seems very slow, SQL being verbose, and you having to write additional wrappers on top of it anyway.

As you write, in practice it sucks for SQL. Formatting is another issue, can become quite awkward in embedded code

> Secondly, you can do that with Path.read_text() and pass it to SQLalchemy-core if a query is so complex you want to

Yes, if you use one file per query. Otherwise you'd need something similar to the naming-scheme of PugSQL, just implemented by your self.

> But writing your entire program like that seems very slow, SQL being verbose, and you having to write additional wrappers on top of it anyway.

This depends entirely on your program and/or problem domain. It might be overkill for simple CRUD applications with a few INSERT/UPDATE/SELECT queries, but might make a lot of sense if you use more advanced SQL features.