That makes a lot of sense. Thanks for the explanation. I will use the
view to convert it to an int.
Jack
On Tuesday, September 17, 2013 1:00:01 PM UTC-7, ke1g wrote:
>
> Yes, this is the expected behavior. The GET parameter is a string, being
> something that is just parsed out of the query
Yes, this is the expected behavior. The GET parameter is a string, being
something that is just parsed out of the query parameter portion of the URL
(which is, itself, a string). There is nothing to inform the code that
parses the query parameters which of the things that might look like
numbers
I am building a search form that provides a drop down list, and then on the
search results, I am redisplaying the search form, but with the search
parameters already pre-selected, so this is what I attempted to do:
{% for item in object_list %}
{{ item.name }}
Hi,
I don´t think using requests objects into templates is a good idea, use request
object in the view so you source the template context with whatever you need.
HTH
El 17/09/2013, a las 20:50, J Y escribió:
> I am building a search form that provides a drop down list, and then on the
> sear
4 matches
Mail list logo
