Inside the template, the travels
field as actually an instance of BoundField
(which is a Django object that binds together the field and its value for rendering). This means the properties are somewhat different.
To iterate over the choices as a tuple:
{% for choice in form.travels.field.choices %}
{{ choice }} -
{% endchoice %}
Produces: (1, 'One') - (2, 'Two') -
To iterate over the elements in the choice tuples separately:
{% for choice_id, choice_label in form.travels.field.choices %}
{{ choice_id }} = {{ choice_label }} <br/>
{% endfor %}
Produces: 1 = One
2 = Two
Hope that helps. Having said that, though, I'm not sure of the context in which you're needing to do this; on the surface, it doesn't seem very django-like. You may find that using a custom form field or a custom template tag gives you a more portable, re-usable implementation that better maintains django's intended separation between view code and template code. Of course, YMMV and it could well be that the direct iteration approach is appropriate for you in this case.