Split library into two parts: DB-API 2.0 compatible and Asyncio style

I am very interested in using this library since type support in psycopg2 is awful to work with. However, some projects still use Python 2.7, and will for another 4 years. Would it be possible to split asyncpg into two parts, one with an asynchronous API, usable with Python 3.5 and above, and one synchronous API that can be compatible across both 2.7 and 3.5 and above?

My proposal is a DB-API 2.0 (PEP 249) compatible API that can be utilized by the asyncio part of the library. The benefits is that applications that do not need asynchronous calls can use the same underlying library as those who do. With this code that doesn't rely on co-routines can use the type support provided by asyncpg.

I haven't used this project yet, or dived into its internals, and don't know whether it is feasible at all to do this. I am just venting my ideas.

Das Issue nennt keine Implementierungsdateien oder Tests. Beginnen Sie mit der Überprüfung der bestehenden asyncio-API von asyncpg und vergleichen Sie die vorgeschlagene synchrone DB-API-2.0-Schnittstelle mit PEP 249 und der Kompatibilität mit Python 2.7. Da es sich um einen explorativen Architekturvorschlag handelt, müssten die Maintainer zunächst Machbarkeit, Umfang und einen messbaren Abschlusszustand definieren.