#8764: Mixing args and **kwargs in reverse() function
-------------------------------------+--------------------------------------
Reporter: tolano | Owner: nobody
Status: reopened | Milestone:
Component: Core framework | Version: SVN
Resolution: | Keywords: reverse function
exception
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by Killarny):
* status: closed => reopened
* resolution: invalid =>
Comment:
I don't understand the rational here for not fixing this issue. The
decision not to allow mixing args and kwargs seems like a lazy way to
avoid coming up with a real solution. Forcing the use of one or the other
but not both is simply not pythonic, and without some sort of discussion,
seems silly. When a python framework does not allow valid python syntax to
function properly, that sounds like a fundamental flaw in design to me.
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 inability to mix them introduces all sorts of complexities to the
logic of the views that shouldn't have to be dealt with. Could anyone
either fix this, or provide some sort of insight as to what the real
rational here is?
--
Ticket URL: <http://code.djangoproject.com/ticket/8764#comment:4>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
