Also, there is a big hope that something like 1.3.1 release will be produced soon as Django 1.3 without r15911 is still IDE unfriendly.
-- Thanks, Dmitry On Thu, Mar 24, 2011 at 6:19 PM, Dmitry Trofimov <trofimov.dmi...@gmail.com> wrote: > Hi Karen, > > r15911 does fix the problem. Thanks. > > You know, people often run code from IDE without debugging. > If you develope in IDE it is convenient to run code from IDE without > switching to console. > > However you are right, that --noreload is nesessary for being able to debug. > > I am unsing and developing PyCharm IDE and it can't debug without > --noreload as debugger in PyCharm knows nothing about new process, > started on autoreload. WingIDE also has that limitation. > > I think it could be fixed in django, but currently I don't know > exactly how. Maybe it should be some option(environment variable) in > Django, which value is used as prefix to command line of a new > process. That prefix could be path to wrapper script of debugger, > which connects to IDE. > > -- > Dmitry > > > 2011/3/24 Karen Tracey <kmtra...@gmail.com>: >> On Thu, Mar 24, 2011 at 7:48 AM, traff <trofimov.dmi...@gmail.com> wrote: >>> >>> Hi guys! >>> >>> Recent commit(r15883), which fixes #15565, indeed brokes execution of >>> django server from IDE on UNIX platforms. >>> >>> What can be done to fix that? >>> >> >> I suspect r15911 will fix it, if the problem is what I'm guessing it is. >> However I am curious about your running with the reloader active under an >> IDE: in my experience with IDEs & Django the reloader breaks the IDE's >> ability to stop at breakpoints. So my assumption was anyone using an IDE >> with Django would generally run with --noreload so as to disable the >> reloader and allow the IDE breakpoint mechanism to function. Are you using >> an IDE that does not need --noreload specified in order for breakpoints in >> the IDE to work? >> >> Karen >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To post to this group, send email to django-developers@googlegroups.com. >> To unsubscribe from this group, send email to >> django-developers+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/django-developers?hl=en. >> > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
