Re: Different behaviour for url parameter in dev run versus test run

2007-11-20 Thread Manoj Govindan
I have raised a ticket for this problem. http://code.djangoproject.com/ticket/5982 I have added the relevant code snippets there. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this

Re: Different behaviour for url parameter in dev run versus test run

2007-11-18 Thread Manoj Govindan
> > I am still not clear about your question. But my guess is that this is > an accepted behaviour. Spaces are read as %20 on URLs. > If you can cut paste the exact sample code on dpaste, some one can > help you > I am aware that spaces are represented as %20 on URLs. My observations were 1) Du

Re: Different behaviour for url parameter in dev run versus test run

2007-11-18 Thread Ramdas S
Not really! I am still not clear about your question. But my guess is that this is an accepted behaviour. Spaces are read as %20 on URLs. If you can cut paste the exact sample code on dpaste, some one can help you RS On Nov 18, 1:59 pm, Manoj Govindan <[EMAIL PROTECTED]> wrote: > On Nov 18, 1

Re: Different behaviour for url parameter in dev run versus test run

2007-11-18 Thread Manoj Govindan
On Nov 18, 12:00 pm, "Ramdas S" <[EMAIL PROTECTED]> wrote: > are u using windows? > I am working on Ubuntu Feisty. Are you suggesting that the behaviour is different on Windows? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Goog

Re: Different behaviour for url parameter in dev run versus test run

2007-11-17 Thread Ramdas S
are u using windows? On Nov 18, 2007 12:41 AM, Manoj Govindan <[EMAIL PROTECTED]> wrote: > > My application has a view that accepts a string parameter and filters > a model based on that parameter. In the development environment the > view works well when passed a string with a space in it, say '

Different behaviour for url parameter in dev run versus test run

2007-11-17 Thread Manoj Govindan
My application has a view that accepts a string parameter and filters a model based on that parameter. In the development environment the view works well when passed a string with a space in it, say 'hello world'. The portion of the url representing the parameter shows up as 'hello%20world'. I th