I'd prefer treating unquoted parameters as variables. If that's not  
possible make url accept a quoted view name and deprecate unquoted  
view names.

Especially unquoted non-ascii strings (as in test url05) are ugly and  
would require hacks or re.LOCALE in my approach in #7806.

Am 20.07.2008 um 20:56 schrieb Malcolm Tredinnick:

>
>
> On Sun, 2008-07-20 at 17:16 +0400, Ivan Sagalaev wrote:
>> Julien Phalip wrote:
>>> Hi,
>>>
>>> For months, there has been a mention in the url tag's documentation:
>>>
>>> "Note that the syntax for this tag may change in the future, as we
>>> make it more robust." [1]
>>>
>>> Is that mention still relevant for 1.0 and beyond?
>>
>> If I recall correctly, there was a discussion that the first  
>> parameter
>> should be changed to work like most other parameters to tags:  
>> treat it
>> literally if it's quoted, otherwise look it up in context. The  
>> objection
>> was that potential benefit wasn't worth the hassle of a backwards
>> incompatible change. But I can't remember if there was a final  
>> decision.
>
> The couple of times I brought it up, it died from a lack of core
> developers really caring that much. I thought it would have been a  
> good
> idea to change it originally. I think it would be a bad idea to change
> it now, since it's been in use for so long. If somebody wants to use
> variables in a url-like tag, it's trivial to write your own variant.
> We're not hurting anybody's software too much by not making the  
> change,
> although it would have been nice to do so for consistency.
>
> I suspect that unless Adrian or Jacob pipe up in the very near future
> with agreement to change it, we can remove that note because the  
> current
> API will be set in stone.
>
> Malcolm
>
>>
>>>
>>
>
>
> >



--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to