This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients ghaering, loewis, nagylzs, r.david.murray
Date 2013-01-14.01:15:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358126158.22.0.0656660966786.issue16958@psf.upfronthosting.co.za>
In-reply-to
Content
B, yes.

So you would view the connection context manager acting as an actual transaction manager as a new feature?  Would you be OK with adding that feature to the existing context manager in 3.4 (since currently the context manager is a noop in autocommit mode), or do you think we need to create a new context manager for this?  Or do we do as the issue that sparked this (issue 8145) suggested, and just document how to create your own?
History
Date User Action Args
2013-01-14 01:16:10r.david.murraysetrecipients: + r.david.murray, loewis, ghaering, nagylzs
2013-01-14 01:15:58r.david.murraysetmessageid: <1358126158.22.0.0656660966786.issue16958@psf.upfronthosting.co.za>
2013-01-14 01:15:56r.david.murraylinkissue16958 messages
2013-01-14 01:15:52r.david.murraycreate