-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugjar doesn't work with Django #8
Comments
Thanks for the report @beatthem. There's two issues here -- Python 2.6 compatibility and Django compatibility. I'll retask this ticket to track the Django issue; I've opened a second issue (#9) to track the Python 2.6 issue. As for the Django issue - There's definitely work to be done here. You need to be using "runserver --noreload --nothreading" to get Django support working at all; but even then, it's quite slow because of the verbosity of the line protocol. This is something that I want to work on when I get a chance, but it's not a small job. I'll leave this ticket open as a marker for the problem. |
I've tried "bugjar manage.py runserver --noreload --nothreading" but it seems to ignore noreload/nothreading options, because I see 3 workers for bugjar itself and 3 workers for bugjar-net in htop (Ubuntu 13.04) With simple "python manage.py runserver --noreload --nothreading" there is only 1 worker, as expected. I've also noticed that 6 processes of bugjar appears before manage.py start to process command line options --noreload and --nothreading. |
I was able to start django server with noreloading and nothreading options; just more patience was needed. bugjar-net creates 2 processes, I think for communication by sockets. |
First, I must say thank you for creating so simple but powerful debugger for python.
Second.
I have troubles with using Bugjar on Django (1.4.10) and Python 2.6.
The text was updated successfully, but these errors were encountered: