#33882: Allow transaction.atomic to work in async contexts.
-------------------------------------+-------------------------------------
Reporter: alex | Owner:
| rajdesai24
Type: New feature | Status: assigned
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: async | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia Bidart):
Replying to [comment:19 Denis Orehovsky]:
> I agree. Why hasn't it been fixed yet? Multiple years have passed
already.
Hello Denis! Please note that this is not a helpful comment, I understand
that you may feel frustrated but I encourage you to consider our
[https://www.djangoproject.com/conduct/ Code of Conduct] in your comments:
> Be friendly and patient.
> Be welcoming.
> Be considerate.
> Be respectful.
> Be careful in the words that you choose.
Django is developed by volunteers who contribute their time when they can.
If you're interested in this feature, it would be fantastic if you could
help by contributing to a solution.
Thank you for your understanding!
--
Ticket URL: <https://code.djangoproject.com/ticket/33882#comment:20>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070192483260f4-ae903aad-6352-4bc8-9b15-19341808d2e0-000000%40eu-central-1.amazonses.com.
