[patch] manage.py: Add support for IP, IP:PORT, or PORT command-line arguments

[jvargas -a-t- acm -*- o r g]

These two files (iputils.py and iputils.diff) add support for IP, IP:PORT, or PORT command-line arguments to manage.py, so that

manage.py runserver [optional port number, or ipaddr:port]

becomes

manage.py runserver [optional ip address, optional port number, or ipaddr:port]

[jvargas -a-t- acm -*- org]

patch for management.py

[jvargas -a-t- acm -*- org]

django/utils/iputils.py module

[jvargas -a-t- acm -*- org]

Note: iputils.py contains doctests (commented out by default)

[jvargas -a-t- acm -*- org]

Added [patch] prefix to ticket summary.

[James Bennett]

How is this different from what runserver already does wrt to specifying port or IP/port? Have I missed something here?

[jvargas -a-t- acm -*- org]

Currently (SVN), you cannot do

$ python manage.py runserver 192.168.1.2

Error: '192.168.1.2' is not a valid port number.

[James Bennett]

Hm. So, really what this should be is just adding support for specifying only an IP and having it bind to the default port on that IP, so that runserver 192.168.1.2 would become functionally equivalent to runserver 192.168.1.2:8000 ?

[jvargas -a-t- acm -*- org]

Indeed, but it also adds some checks for validity (see iputils.py file) and unit tests.

[Adrian Holovaty]

This doesn't introduce any new functionality, so I'm marking it as a wontfix. It's really not a big deal to have to specify the port if you want to use a custom IP address.

As an aside, I'm always hesitant to add more stuff to django.utils, so that fact played into this decision.

[(none)]

Milestone Version 1.0 deleted