#24574: 'python manage.py runserver' sleeps forever because of threading lock
-------------------------------------+-------------------------------------
Reporter: s2krish | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: needsinfo
Keywords: threading lock, | Triage Stage:
manage.py | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* resolution: => needsinfo
Comment:
First, you [https://docs.djangoproject.com/en/1.7/ref/django-admin
/#runserver-port-or-address-port shouldn't use runserver in production].
DO NOT USE THIS SERVER IN A PRODUCTION SETTING. It has not gone through
security audits or performance tests. (And that’s how it’s gonna stay.
We’re in the business of making Web frameworks, not Web servers, so
improving this server to be able to handle a production environment is
outside the scope of Django.)
Anyway, it seems more likely to be a mistake in your code or configuration
as we have many people using Django 1.7 runserver without a problem.
Please reopen if you can provide more details about how we can reproduce
the problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/24574#comment:5>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.df7c02e728965515ecee1abb091a8458%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.