Thanks for both of your ideas. Joshua: It is stopping on the first line of code, and I can step through the manage.py module and if I recall (I'm not in front of my computer at the moment) it catches breakpoints in other files (ex: settings.py) in the initial load. What I can't seem to get is breakpoints triggered by the browser. Have you ever had success with that? Is it possible using Django's development server? Using any server?
Daniel: Will pdb breakpoints be triggered by requests from the browser? What I'm really looking for is the ability to access a url in my browser and step through the whole process of resolving a request on the Django end. If this is possible, how do I do it? If it isn't possible, why, and is there a way to jerry-rig it? Maybe passing an artificially constructed request object to the view function--though that sounds like a big time drain. This seems like a problem that most developers must hit from time to time. How has the community approached it in the past? Thanks again, everyone, Kevin On Mon, Sep 21, 2009 at 5:18 AM, Joshua Russo <josh.r.ru...@gmail.com>wrote: > On Mon, Sep 21, 2009 at 10:15 AM, Joshua Russo <josh.r.ru...@gmail.com>wrote: > >> >> On Sep 21, 6:00 am, Kevin Bache <kevin.ba...@gmail.com> wrote: >> > Hi Everyone, >> > I'm a bit of a Django noob so please forgive me if my hope here is >> > swimmingly optimistic: >> > >> > I'd like to be able to set breakpoints in my django project which would >> be >> > triggered by my browser's requests to the integrated Django development >> > server. Is this possible? I'm using NetBeans 6.7 with Python EA as my >> > IDE. I have manage.py set as the project's main module and "runserver >> > --noreload" for arguments. I set sample breakpoints in my urls.py >> module >> > and run the server by selecting Debug >> Debug Main Project in NetBeans, >> but >> > when I surf around the website through Firefox, the requests fly right >> past >> > my breakpoints. Am I missing something or is this just some web dev >> pipe >> > dream? If what I'm trying for is impossible, what are some realistic >> > debugger usage scenarios with Django? My development will go much >> faster if >> > I can pause and look around every now and again without having to splice >> my >> > code with print statements. >> >> It may be the way you are running the program from NB. There are 2 >> buttons, Run Main Project and Debug Main Project. Make sure you are >> using the second. It should automatically break on the very first line >> of code (at least it did in 6.5), where you need to hit continue to >> actually run the project. Personally I found that particular feature >> an annoyance and a blessing. An annoyance because you always have to >> click 2 buttons to really start the debug process, a blessing in that >> when I first started with both Django and Python were new to me and it >> helped me get my head around how the entire process got off the >> ground. > > > Some day I might actually start reading a little better. You are doing > things properly. Is it stopping at the first line in the manage.py file when > you debug? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
