Allow namespaced reusable app urls as ROOT_URLCONF

2018-02-15 Thread Vlastimil Zíma
Hi, I've tried to understand how to write an urls module for reusable app and I think I have it correctly: # myapp.urls app_name = 'myapp' urlpatterns = [ url(r'^index/$', MyIndexView.as_view(), name='index'), url(r'^form/$', MyFormView.as_view(), name='form'), ... ] In code I use

Re: Allow namespaced reusable app urls as ROOT_URLCONF

2018-02-15 Thread Florian Apolloner
Hi, On Thursday, February 15, 2018 at 2:40:07 PM UTC+1, Vlastimil Zíma wrote: > Is there a reason not to use namespace from root urlconf? Can we change > that, i.e. make root resolver to load the app_name of the root urls? Did I > missed something else? > I don't think there is any reason to n

Re: Allow namespaced reusable app urls as ROOT_URLCONF

2018-02-15 Thread Tim Graham
The issue was raised some months ago in https://code.djangoproject.com/ticket/28413 and came to a similar conclusion. The resolution was to document the restriction. On Thursday, February 15, 2018 at 10:57:54 AM UTC-5, Florian Apolloner wrote: > > Hi, > > On Thursday, February 15, 2018 at 2:40:

Re: Consider renaming `mark_safe` to `dangerously_trust_html` (etc)

2018-02-15 Thread Douglas Miranda
I think this can mislead the developers to think mark_safe solves it all. The forums are full of answers with *Use mark_safe;* *Use htmlfield|safe;* Maybe Django should start warning about mark_safe on the logs, then change the behavior. (Or even deprecate and remove) Things like this we tend