#27262: Delegate URL resolver checks to URL classes
-------------------------------------+-------------------------------------
Reporter: Sjoerd Job Postmus | Owner: Lucas
Type: | Lois
Cleanup/optimization | Status: assigned
Component: Core (URLs) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sjoerd Job Postmus):
Hi Lucas Lois,
Great to hear you are interested in working on this Django ticket.
I have already started the implementation of this a while ago. I pushed my
changes today, to my fork on github (after your post).
Seeing as you are also interesting on working on this ticket, I would be
happy to not create a pull request and give you a chance to also implement
this. I'd be happy to also review of your changes.
If instead you'd prefer to not duplicate the effort and choose another
ticket, go ahead and I'll create a pull-request of my changes.
Your implementation plan makes sense to me, although you should be aware
of the recursive nature of URL resolvers.
Kind regards,
--
Ticket URL: <https://code.djangoproject.com/ticket/27262#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 [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/067.41141d1421181da8d2b1a972269efc10%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
