I've noticed that "transaction already in progress" warnings and errors are emitted by Postgres when pretty much any operation is executed from yoyo. The following is an output of the Postgres logs when running yoyo list against a brand new install of Postgres with two SQL migration files.

2022-11-21 16:04:13.787 UTC [98] WARNING:  there is already a transaction in progress
2022-11-21 16:04:13.794 UTC [98] WARNING:  there is already a transaction in progress
2022-11-21 16:04:13.799 UTC [98] WARNING:  there is already a transaction in progress
2022-11-21 16:04:13.800 UTC [98] ERROR:  table "yoyo_tmp_0BMPaCKDqU" does not exist
2022-11-21 16:04:13.800 UTC [98] STATEMENT:  DROP TABLE "yoyo_tmp_0BMPaCKDqU"
2022-11-21 16:04:13.802 UTC [98] WARNING:  there is already a transaction in progress
2022-11-21 16:04:13.818 UTC [98] WARNING:  there is already a transaction in progress
2022-11-21 16:04:13.838 UTC [98] WARNING:  there is already a transaction in progress

Maybe related to #71?

+1 I'd like to use psycopg3 in a new project and not have psycopg2 as an additional dependency.