Re: Reverse URL resolver fails with a literal dot

2007-05-25 Thread Olivier Guilyardi
akonsu wrote: > yes, it is an innovative feature. i think it is difficult to implement > right. the general problem in my understanding is to be able to > generate a regex that accepts a (partial) input string. then, to > compare the generated regex with the list in the urls module. this > involve

Re: Reverse URL resolver fails with a literal dot

2007-05-25 Thread Olivier Guilyardi
Malcolm Tredinnick wrote: > On Fri, 2007-05-25 at 11:07 +0200, Olivier Guilyardi wrote: >> Malcolm Tredinnick wrote: >> This seems to mean that the resolver and the reverse resolver are not symmetrical. Is this a bug? >>> It is. There's a sort of correct patch to fix a few things like th

Re: Reverse URL resolver fails with a literal dot

2007-05-25 Thread akonsu
yes, it is an innovative feature. i think it is difficult to implement right. the general problem in my understanding is to be able to generate a regex that accepts a (partial) input string. then, to compare the generated regex with the list in the urls module. this involves programming language t

Re: Reverse URL resolver fails with a literal dot

2007-05-25 Thread Malcolm Tredinnick
On Fri, 2007-05-25 at 11:07 +0200, Olivier Guilyardi wrote: > Malcolm Tredinnick wrote: > > >> This seems to mean that the resolver and the reverse resolver are not > >> symmetrical. Is this a bug? > > > > It is. There's a sort of correct patch to fix a few things like this in > > Trac, so we'll

Re: Reverse URL resolver fails with a literal dot

2007-05-25 Thread Olivier Guilyardi
akonsu wrote: > i would say that yes it is a bug. i have seen many bugs in the reverse > resolver code. for example, it crashes (throws a python exception) if > a regex pattern contains question marks (optional elements) and i am > sure it has a lot more. my personal opinoin is that this code is >

Re: Reverse URL resolver fails with a literal dot

2007-05-25 Thread Olivier Guilyardi
Malcolm Tredinnick wrote: >> This seems to mean that the resolver and the reverse resolver are not >> symmetrical. Is this a bug? > > It is. There's a sort of correct patch to fix a few things like this in > Trac, so we'll get to checking it in at some point. Should I post a ticket? Regards,

Re: Reverse URL resolver fails with a literal dot

2007-05-24 Thread Malcolm Tredinnick
On Thu, 2007-05-24 at 19:00 +0200, Olivier Guilyardi wrote: > Hi, > > In my urls.py I have the following entry: > > url(r'^items/download/(?P[0-9A-Za-z._:%?-]+)\.(?P[0-9a-z]+)$', > web_view.item_export, > name="telemeta-item-export"), > > In my template: > {% url telemeta-item-e

Re: Reverse URL resolver fails with a literal dot

2007-05-24 Thread akonsu
hello, i would say that yes it is a bug. i have seen many bugs in the reverse resolver code. for example, it crashes (throws a python exception) if a regex pattern contains question marks (optional elements) and i am sure it has a lot more. my personal opinoin is that this code is simply a hack.