Hello everybody. Ramiro Morales and me were working on this ticket #15294 [0] and Julien linked this one #8001 [1]. We had a little discussion about two possible solution for #8001 and Julien suggested that we should hear your opinion (you can read all comments on ticket #15294).
The discussion was about if we have to take care of backward compatibility on this issue. I uploaded two patches to #8001, one of them taking care of backward compatibility. I think that the reason for keeping backward compatibility, is just that it is good. And the reasons for deprecating the old behavior are: - Cleaner code. - This is not a documented part of Django's API, so we either can or cannot take care of backward compatibility. - I don't like to put any ugly try/catch. I'm sorry for my English. Regards, Dario Ocles (burzak). [0] http://code.djangoproject.com/ticket/15294 [1] http://code.djangoproject.com/ticket/8001 -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
