#31070: Add a check for URLconfs that mix named and unnamed capture groups
-------------------------------------+-------------------------------------
Reporter: Baptiste Mispelon | Owner: Baptiste
| Mispelon
Type: New feature | Status: closed
Component: Core (System | Version: master
checks) |
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: assigned => closed
* resolution: => needsinfo
Comment:
HI Baptiste. Right, thanks for working with me.
My suspicion here is that things are fine as they are. Let's leave off
adding the warning, at least for now.
(I hope that makes sense, I think it does given the conversation...)
> ...first step of a deprecation path that would end...
If you think there's a real gain to be had, I'm happy if you want to flesh
that out a little bit and take it to the mailing list to see if folks
think it worth the churn.
(That could well be...) If so we can re-open and push on with that.
--
Ticket URL: <https://code.djangoproject.com/ticket/31070#comment:12>
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.9b741ad1d73456d04ef6d7777f8f90ca%40djangoproject.com.
