Michael Richardson wrote: > With these cases (the former more so than the latter) you are creating > URLs for an entirely separate project, not your own, essentially.
Not "entirely separate". These are projects sharing much of the codebase, just having different SITE_ID in settings. Anyway there's still my first use-case of constructing URLs from standalone scripts. > We pass around request objects all over the place in order to get this > functionality. request.build_absolute_uri is great, but it does > require that request object and passing it around - which sucks. request.build_absolute_uri works for you because you don't have those use-cases. This is why we see this way differently: you think that having a request universally available makes things more convenient while in my view it doesn't fix URL construction at all[*] and just adds a bit to the mess in thread-locals. And I kind of disagree that my use-cases very exotic. [*] URL construction is really broken right now because I am forced to hard-code 'http://' or 'https://' in my script that sends mail by cron. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
