#4304: a second dev. web server does not report an err if bound to the same port
-------------------------------------+-------------------------------------
Reporter: rogerpack2005@… | Owner: adrian
Type: Uncategorized | Status: new
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by hamidhaghshenas):
* status: closed => new
* severity: => Normal
* resolution: fixed =>
* easy: => 0
* ui_ux: => 0
* type: => Uncategorized
Comment:
Replying to [ticket:4304 rogerpack2005@…]:
> So...seems that on win32 (at least) if you start a server python
manage.py runserver
> then start another
> python manage.py runserver
> the first is really running, and the second doesn't an error but happily
tells you it is running. This is a problem at times :) Thanks!
I have the same problem with Django 1.10.1 and Windows 7 64-bit.
I was started a Django project on port 8000, then created a new Django
project (with Django 1.10.1) and ran the server.
It said that the server has been started successfully on port 8000, but
browsing localhost:8000 showed the previous project's page.
--
Ticket URL: <https://code.djangoproject.com/ticket/4304#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/081.5654fb438b9a17985153811b1ad7c314%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
