Quick hack that provides a runconcurrentserver command, broadly similar to Django ticket:3357 without patching Django itself
Remove an iota of whitespace.
|django_concurrent_test_server||Calling super with SocketServer.ForkingMixIn as the type seems to be …|
|.gitignore||Ignore some stuff. Boring stuff.|
|LICENSE||Remove whitespace [Gun.io WhitespaceBot]|
|README||RUNSERVER_DEFAULT_ADDR / RUNSERVER_DEFAULT_PORT in settings.py overri…|
|setup.py||setup-ify ready for PyPI and beyond|
============================= django_concurrent_test_server ============================= <http://code.djangoproject.com/ticket/3357> is a Django ticket about making the built-in dev server concurrent. This isn't going to happen any time soon, but one of the comments wondered about turning the patch in the ticket into a separate app that could be dropped in to provide a concurrent dev server as a new command. This is what django_concurrent_test_server does. Note that with the forking server, it is possible for a child process to survive when the parent dies; the child retains the open listen socket, so you have to find it and kill it before restarting the server. It should be possible to fix this, but I haven't looked into it yet; unless you are aware of threading problems in your code or extensions, you should probably use that for preference. Almost all the work was done by Istvan Albert, as per <http://is.gd/1h6JX> on <http://groups.google.com/group/django-developers/>. Additionally I've duplicated the runserver command from Django itself, and repackaged the whole lot. Given the context of the original discussion, and the presence of the patch on the Django ticket, I'm distributing this under the Django license with the normal "Django Software Foundation and individual contributors" copyright statement. James Aylett <http://tartarus.org/james/computers/django/> Usage ===== 1. Drop the django_concurrent_test_server directory somewhere on your PYTHONPATH 2. Add django_concurrent_test_server to your INSTALLED_APPS 3. If threads worry you, and bearing the above warning in mind, set CONCURRENT_THREADING = False in settings.py to use forking 4. Use ./manage.py runconcurrentserver to start a concurrent server 5. (optional) Add CONCURRENT_RANDOM_DELAY = True to your settings.py to introduce a small, random delay into each request; useful for finding race conditions. (By <http://github.com/wolever>.) 6. (option) Set RUNSERVER_DEFAULT_ADDR / RUNSERVER_DEFAULT_PORT in settings.py to override the defaults without having to hack the code. Useful for people who don't like aliases, or move things between machines a lot.