dktc <[email protected]> added the comment: No worries, I understand this sort of bug is not easy to reproduce, but that's exactly why IMHO this should be looked into as some pretty rigorous testing. I'd like to be able to run PyPy in production under heavy load in multi-processing / multi- threaded environment and looks like it might uncover a few issues like this.
I'd definitely suggest setting up Django and doing more testing under it as a common real-world scenario. Here is the tutorial on what you need to do after "pip install django". I suggest you try the tutorial app: https://docs.djangoproject.com/en/1.5/intro/ Note, that most of the likely issues here are not in Django itself, but in Spawning/Eventlet which act as Django's WSGI container and heavily rely on Python's multi-processing / multi-threading facilities - where the likely problems are. Most of the tracing to do is within Spawning code, specifically spawning_child.py and spawning_controller.py Spawning is based on Eventlet and can be set up according to the Github instructions. I recommend getting the latest from Github as it contains a Django 1.5 compatibility fix: "pip install -e git+http://github.com/rtyler/spawning.git#egg=spawning"; Hope this helps with getting started on this issue. ________________________________________ PyPy bug tracker <[email protected]> <https://bugs.pypy.org/issue1509> ________________________________________ _______________________________________________ pypy-issue mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-issue
