Re: Ticket 8764 (Mixing args and **kwargs in reverse() function)

2009-01-07 Thread Alex Gaynor
Yes, please do open a ticket for those. Alex On Wed, Jan 7, 2009 at 11:37 AM, Luke Graybill wrote: > I hadn't intended to come off like an ingrate or be dismissive in my post, > and I apologise for sounding that way; I was frustrated when I wrote it, > which was a mistake.

Re: Ticket 8764 (Mixing args and **kwargs in reverse() function)

2009-01-07 Thread Luke Graybill
I hadn't intended to come off like an ingrate or be dismissive in my post, and I apologise for sounding that way; I was frustrated when I wrote it, which was a mistake. I have great respect for the development efforts for Django, and the polite comments in response to my post have only increased

Re: Ticket 8764 (Mixing args and **kwargs in reverse() function)

2009-01-07 Thread mrts
On Jan 7, 3:43 am, Malcolm Tredinnick wrote: > On Tue, 2009-01-06 at 15:38 -0800, Killarny wrote: > > There are many instances where, in a complicated implementation of > > views, one might want to have a combination of required args and > > optional kwargs, and the

Re: Ticket 8764 (Mixing args and **kwargs in reverse() function)

2009-01-06 Thread Malcolm Tredinnick
On Tue, 2009-01-06 at 15:38 -0800, Killarny wrote: > The above ticket was opened a while back concerning the inability to > define views that use both positional arguments and keyword arguments > when expecting to use reverse() to match urls tied to those views. > > I don't understand the

Ticket 8764 (Mixing args and **kwargs in reverse() function)

2009-01-06 Thread Killarny
The above ticket was opened a while back concerning the inability to define views that use both positional arguments and keyword arguments when expecting to use reverse() to match urls tied to those views. I don't understand the rational here for not fixing this issue. The decision not to allow

Re: ticket 8764 (Mixing args and **kwargs in reverse() function)

2009-01-06 Thread Killarny
The above ticket was opened a while back concerning the inability to define views that use both positional arguments and keyword arguments when expecting to use reverse() to match urls tied to those views. I don't understand the rational here for not fixing this issue. The decision not to allow