Hi, > On 30 apr 2015, at 18:42, Carl Meyer <c...@oddbird.net> wrote: > > transaction-hooks is actually fairly small and understandable too. And I > don't think it's hard to use for this situation, either; you'd just need > to use `connection.on_commit` in your signal handler if you wanted to > delay some action until post-commit. > >> Unless it's going to be super easy to port transaction-hooks over, I >> think it might be nice to get this in and sealed (it's not adding too >> much more complexity). If transaction-hooks would land in core well, >> let's do that. > > I don't think landing transaction-hooks in core for 1.9 would be hard at > all, and no-one has objected to the idea (AFAIK). I (or anyone really) > just need to get around to it. Motivation has been low so far mostly > because it works fine as an external add-on.
I did an initial port of django-transaction-hooks, it was pretty straightforward. All the hard work has already been done. :-) Here is the PR: https://github.com/django/django/pull/4593 The patch is not yet finished (there’s a todo-list at the PR with some missing pieces). Let me know what you think and I’ll be happy to continue working on a proper patch to get it into a merge-able state. Cheers, Andreas -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5A9C5A84-A28C-4556-BD7F-7F1699A166AA%40pelme.se. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
