Why transaction support implemented only for SAConnection?

[laz2]

I see only dependency from SA in xid generation. Other code uses basic aiopg and plain sql for work with transactions.

[asvetlov]

You can run raw SQL transactions by executing BEGIN/COMMIT/ROLLBACK statements

[laz2]

Yes. But without context manager and nested transaction it is not so comfortable. Do aiopg members have any reasons about this place of transactions code? May someone provide pull request with more generic transaction support?

[asvetlov]

If you want to make a PR -- you a welcome

[vir-mir]

Hi!
I'm doing a transaction.
but my class tied to https://docs.python.org/3.5/library/typing.html
which appeared only in 3.4
Maybe add compatibility https://docs.python.org/3.5/library/typing.html
Or better to rewrite?

@asvetlov @jettify

[jettify]

What features do you need? It is possible to write async context managers in backward compatible way: https://github.com/aio-libs/aiopg/blob/master/aiopg/cursor.py#L380-L403 For what purpose do you need typing?

[vir-mir]

The fact that I have written it long time ago,only not cover the tests and docs
But it is written in python3.5 with PEP484

But I looked at your code, very little corrections that-be to bring it to the PEP3170

I will cook PR

[Pliner]

It looks like the issue was resolved by #219