Avoided ambiguous output when runserver port is already in use.

Thanks James Pic for the suggestion (PR 88).
This commit is contained in:
Aymeric Augustin 2013-02-01 22:25:29 +01:00
parent d75a54c184
commit 0412b7d280
2 changed files with 2 additions and 2 deletions

View File

@ -93,7 +93,7 @@ class Command(BaseCommand):
self.stdout.write(( self.stdout.write((
"%(started_at)s\n" "%(started_at)s\n"
"Django version %(version)s, using settings %(settings)r\n" "Django version %(version)s, using settings %(settings)r\n"
"Development server is running at http://%(addr)s:%(port)s/\n" "Starting development server at http://%(addr)s:%(port)s/\n"
"Quit the server with %(quit_command)s.\n" "Quit the server with %(quit_command)s.\n"
) % { ) % {
"started_at": datetime.now().strftime('%B %d, %Y - %X'), "started_at": datetime.now().strftime('%B %d, %Y - %X'),

View File

@ -138,7 +138,7 @@ see the following output on the command line:
0 errors found 0 errors found
|today| - 15:50:53 |today| - 15:50:53
Django version |version|, using settings 'mysite.settings' Django version |version|, using settings 'mysite.settings'
Development server is running at http://127.0.0.1:8000/ Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C. Quit the server with CONTROL-C.
You've started the Django development server, a lightweight Web server written You've started the Django development server, a lightweight Web server written