2010/12/31 Łukasz Rekucki <[email protected]>: > Hi, > > I'm not sure about resolution for this ticket[1]. Initially this looks > like a regression. On the other hand, it was never documented that > "runserver" accepted anything other than an IP:port pair. > > 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. > > If anyone thinks this is useful, I'll make a patch to fix and document this.
I've certainly used localhost, and on more than one occasion, I seem to recall using another host name. However, you're correct in saying that using a hostname was never documented behavior, either in the docs, the runtime help for the runserver command, or in the docstring for runserver. I'm happy to let the resolution be shaped by the fix. If we can fix this easily and robustly, then we might as well allow hostnames (and update documentation to reflect this). However, if fixing the problem will require an error-prone solution, or an excessively complex solution, I'm happy to call this a wontfix. Yours, Russ Magee %-) -- 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.
