On 31 December 2010 05:44, Simon Meers <[email protected]> wrote: > >> I don't know how many people actually used that feature (I never did), >> but it seems like it was a bit accidental. As we are speaking about a >> development server, I don't find this feature very useful as (most of >> the time) you want to run it on a host-only address, which won't have >> many aliases other than "localhost". You could add more in your >> "hosts" file or have a DNS on intranet map to your machine, but it >> sounds like a really rare case. > > I actually use this all the time; my /etc/hosts has an entry for almost > every Django project I work on; this way the browser maintains separate > cookies for each one, so I don't have to keep logging in/out, etc. I'd be > very disappointed to see this functionality disappear.
Me too, but all the names point to 127.0.0.1. AFAIK, this doesn't affect cookies, 'cause they are assigned to the domain name, not IP addresses. I can only see this useful if you need to run more then one devserver at the same time and don't want to remember different IPs for each of them. I'll go with Russel's advice and see how hard the fix is. Thanks for comments and Happy New Year :) Łukasz Rekucki -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
