I'd really, really like an alternate URL resolver which does typecasting. I mean, if I'm specifying the type right there, why not expect the resolved to be the type I just specified? In 995 of URLs, you're talking about three basic types anyway: strings, integers, and (increasingly) UUIDs. After 5 years it still trips me up when I do a comparison with a number grabbed from a URL and, say, Object.otherobject_id.
On Thursday, September 15, 2016 at 3:52:46 AM UTC-5, Sjoerd Job Postmus wrote: > > > > To me, that settles it: no typecasting. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0032720b-b1a7-4050-88f3-4fef45027d46%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
