#27762: Concurrency Safety Documentation
-------------------------------+--------------------------------------
Reporter: Kevin Mahoney | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Kevin Mahoney):
Yes, I'm referring to the atomic increment and the concurrent modification
(bug 2 & 3) in the post. You're right that I didn't spot the note which
covers the atomic increment nicely and I'm glad there is a ticket for the
other issue.
In my personal opinion you should not show incorrect code to a learner,
and shielding them from this complexity may be doing more harm than good.
This opinion is reinforced for me when I see how common these bugs are in
commercial and open source code. But this can be a discussion for another
time...
The main purpose for this ticket is to see if there is an appetite for
concurrency documentation covering concurrent modification and maybe a
note about how this is affected by isolation levels. I had in mind a
section in the ORM guide called something like 'concurrency safety'. What
do you think?
--
Ticket URL: <https://code.djangoproject.com/ticket/27762#comment:2>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.fad94b4122eed22e02c44f0f9beb71ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
