Hi Thomas,
On Thursday, April 16, 2015 at 10:21:04 AM UTC+2, guettli wrote:
>
> I talked about this in our team. The pace is to fast.
>
FWIW, every feature changed/deprecated goes through the same (fast) cycle.
If you need slower changes, please stay with LTS versions. Granted, you
still have to change your code at some point, but not that rapidly…
We have about thousand urls mappings that need to be changed to from
> reverse('mapp.views.foo.bar') to reverse(view_method).
>
You can just write your own url() which sets this as name, all the reverses
can stay the same
What do you gain be disabling this feature? Security is not a concern any
> more.
>
A single codepath and nicer error handling, ie you'd get a normal python
import error when the import in urls.py failed. Before that Django often
masked errors in the string import mechanism etc…
> We think disabling this feature brings drawbacks without advantage.
>
Clear and understandable error messages that are thrown at the point where
they should have been is a big adventage for me personally (and from my
experience in #django, many people welcomed that change :))
Cheers,
Florian
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/508e21d3-a502-4e5a-a588-7da432431d93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
