#31070: Add a check for URLconfs that mix named and unnamed capture groups
-------------------------------------+-------------------------------------
Reporter: Baptiste Mispelon | Owner: Baptiste
| Mispelon
Type: New feature | Status: assigned
Component: Core (System | Version: master
checks) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Hi Baptiste.
Thanks for taking to the time to clarify/expand.
> ...assume that the current pattern was working correctly as-is.
Hmm. In that case I'm not sure of the value here.
From #31061, I had it in my mind that there was an actual error in play.
(But if an optional capture group—`(?P<...>...)?` fails to match, I guess
the positional args might still come into play...)
That not being the case I'm not sure we should start raising a warning for
code that has no-doubt been working for years.
(We get a lot of complaints when we do that, rightly I think)
I'd lean to `wontfix` in that case. What do you think?
--
Ticket URL: <https://code.djangoproject.com/ticket/31070#comment:5>
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/067.44d775ae9cc4d94bed43a44aae0fbfde%40djangoproject.com.
