#31069: Change in behavior for optional re matches.
--------------------------------+------------------------------------
Reporter: Terence Honles | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 3.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+------------------------------------
Comment (by Terence Honles):
Thanks @jishansingh, yes, I forgot the last `?` when typing the example
into the report.
@felixxm it would be best if this was fixed (documented) sooner rather
than later so people migrating would know they need to fix it. We didn't
have appropriate test coverage, but one of my coworkers noticed it by
chance (not a frequently used route), and checked the rest of our
application to make sure there weren't any offenders.
I don't know where to put any documentation, but I'm willing to help call
it out if I'm pointed in the right direction (I may not have time next
week so if someone else can get to it that would be great, otherwise I'll
see what I can do).
--
Ticket URL: <https://code.djangoproject.com/ticket/31069#comment:6>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.887be5d6d59acdf8b8d3be89e97d1600%40djangoproject.com.
