On Thursday, September 22, 2016 at 5:39:31 PM UTC+2, Alasdair Nicol wrote:
> On Thursday, 22 September 2016 15:59:12 UTC+1, Sjoerd Job Postmus wrote:
>> Another part I see is that the high coupling between Django and the URL 
>> resolvers (as mentioned in 
>> http://sjoerdjob.com/post/is-djangos-url-routing-tightly-coupled/ ) 
>> should probably be cleaned up, if it is desired to someday support 
>> alternative URL resolvers. I'm willing to provide a patch for the checking 
>> part, but I'm not sure if it would be accepted. Do I need to open a ticket 
>> for that?
>> I wrote the initial url checks code. The current tight coupling is the 
> way the code turned out, it wasn't a deliberate design choice on my part. I 
> read your blog post, and changing the code as you suggest so that the 
> resolver can check itself sounds good to me. Yes, please open up a ticket 
> to go with your patch.
> Cheers,
> Alasdair


Thank you for your feedback. I created the ticket: 
https://code.djangoproject.com/ticket/27262. I'm not sure on what timescale 
I can supply a patch though. Should it be marked as easy picking in the 
hope somebody else can take it up?

I hope I did not offend you with my post on how the code turned out. That 
was not my intention, but if it did offend you: my apologies.

Kind regards,
Sjoerd Job

You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to