Hi Thomas,
I appreciate your concern, and it's a significant change for your
application, which is obviously very large and has been in development for
some time. I've been involved with similarly painful processes such as the
transition to the {% url %} tag requiring a string.
First a note on th
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 t
Am Thu, 16 Apr 2015 01:21:04 -0700 (PDT)
schrieb guettli :
> We never jumped on the "give the URLs a name" wagon.
Why don't you go with Tim's idea to implement a custom url() method to
automatically give the views their path as URL names? This should be
rather easy and you should be able to do the
Dear Graham and django developers,
I talked about this in our team. The pace is to fast. We have about
thousand urls mappings
that need to be changed to from reverse('mapp.views.foo.bar') to
reverse(view_method).
We never jumped on the "give the URLs a name" wagon.
What do you gain be disablin
