add coercion to URLconf

[klrfin@…]

I'm thinking of a coercion feature similar to TypedChoiceField. The dict could contain the coercions. So if I have a route w/ a parameter X, the dictionary could be:
{'coerce': {'x': int}}

[Chris Beaven]

I don't see the necessity.

Coerce it in your view, or if it's a common case, use a decorator to do the coercion (you can even use this decorator directly in the url conf).

[notcourage]

Seems to me the whole point of routes is to express URL syntax. So far I've written 3 regex's over & over: string, sha1, int. Wouldn't it be nice to declare the type instead of the regex? No regex to repeat and coercion. Thx for considering it.