#26888: RegexURLResolver doesn't work in threaded environments -------------------------------------+------------------------------------- Reporter: MarkusH | Owner: knbk Type: Bug | Status: closed Component: Core (URLs) | Version: 1.10 Severity: Release blocker | Resolution: fixed Keywords: | Triage Stage: Ready for | checkin Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>): In [changeset:"06323dafc7fd380609e5cb5d6a62a4a229cc06d3" 06323da]: {{{ #!CommitTicketReference repository="" revision="06323dafc7fd380609e5cb5d6a62a4a229cc06d3" [1.10.x] Fixed #26888 -- Fixed concurrency issue in URL resolver. Fixed a regression in 625b8e9295d79650208bfb3fca8bf9e6aaf578e4: improper short-circuiting could lead to a KeyError when threads concurrently call RegexURLResolver._populate(). Backport of 389a5318a06e7e4d8f8aba14af88c4cc4ea0db47 from master }}} -- Ticket URL: <https://code.djangoproject.com/ticket/26888#comment:4> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/065.0ade1d210b72d3b9cc5f7423b678f139%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.