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 aymeric.augustin
Recipients Jeremy Banks, Mark.Bucciarelli, Ronny.Pfannschmidt, adamtj, asvetlov, aymeric.augustin, bulb, dholth, flox, ghaering, monsanto, pitrou, r.david.murray, scott.urban, torsten, tshepang, zzzeek
Date 2014-06-06.14:10:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402063855.07.0.755308368881.issue10740@psf.upfronthosting.co.za>
In-reply-to
Content
I'm attaching a documentation patch describing improvements of the transaction management APIs that would address this issue as well as three others.

It's preserving the current transaction handling by default for backwards compatibility. It's introducing two new, more simple and less surprising transaction modes.

Could someone have a look and tell me if such improvements seem reasonable? If so, I'll try to write a patch targeting Python 3.5.
History
Date User Action Args
2014-06-06 14:10:55aymeric.augustinsetrecipients: + aymeric.augustin, ghaering, pitrou, Jeremy Banks, r.david.murray, zzzeek, asvetlov, flox, adamtj, dholth, torsten, monsanto, scott.urban, tshepang, Ronny.Pfannschmidt, Mark.Bucciarelli, bulb
2014-06-06 14:10:55aymeric.augustinsetmessageid: <1402063855.07.0.755308368881.issue10740@psf.upfronthosting.co.za>
2014-06-06 14:10:55aymeric.augustinlinkissue10740 messages
2014-06-06 14:10:54aymeric.augustincreate