Thanks for the pointer to previous discussion, will review and see if I can contribute something useful.
Cheers, Alex On Sep 6, 12:58 am, Karen Tracey <[email protected]> wrote: > On Sun, Sep 6, 2009 at 12:16 AM, vegas <[email protected]> wrote: > > > Hi guys, > > > I was just doing some work, and I noticed that passing args and kwargs > > to reverse raises an exception which explicitly tells me not to do > > that: > > if args and kwargs: > > raise ValueError("Don't mix *args and **kwargs in call to > > reverse()!") > > I don't see an obvious reason for this to be the case, and looking at > > the end of the method, if search fails then a NoReverseMatch exception > > is raised with error text that leads me to believe that either at one > > point args and kwargs were mixable, or people would like them to be. > > > I'm a far cry from a django developer, but I could probably rustle up > > a patch to make args and kwargs acceptable for reverse toward the end > > of next week if someone hasn't already done this and it's considered > > desirable. > > Are you sure it is as easy as you think? This has been requested: > > http://code.djangoproject.com/ticket/8764 > > and discussed: > > http://groups.google.com/group/django-developers/browse_thread/thread... > > before. I don't get the idea it is that easy to do efficiently and without > confusing-for-users limitations on when mixing will and will not work. > > Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
