search

thecocce / pyscripter

Automatically exported from code.google.com/p/pyscripter
0 stars 0 forks source link

Breakpoints fail #321

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. debug a django app
2.
3.

What is the expected output? What do you see instead?
A set breakpoint does not get hit

What version of the product are you using? On what operating system?
python 2.6.2 pyscripter 1.9.97 rpcy 3.0.6

Please provide any additional information below.

Original issue reported on code.google.com by Pete.Do...@gmail.com on 13 Jul 2009 at 5:52

GoogleCodeExporter commented 9 years ago 
Pls see 
http://code.google.com/p/pyscripter/wiki/FAQ#How_can_I_debug_Django_applications
?

Original comment by pyscripter on 3 Jan 2010 at 1:24

GoogleCodeExporter commented 9 years ago 
I have the same problem. Breakpoints in my settings.py works, but breakpoints 
in my
views.py or models.py doesn't work. That means, when the django developer 
server is
starting, the breakpoints work. When the django developer server is started and
handling request, breakpoints no longer work.

My environment is python 2.5.1 pyscripter 1.9.9.7, rpyc-2.60, win xp sp2.

Original comment by linna...@gmail.com on 16 Mar 2010 at 4:21

GoogleCodeExporter commented 9 years ago 
The problem is that currently pyscripter does not support debugging other 
threads than the main (pdb limitation).  The instructions above used to work.  
Don't they still?  Otherwise the issue has to wait until multi-threaded 
debugging is supported.

Original comment by pyscripter on 11 Aug 2010 at 11:00

GoogleCodeExporter commented 9 years ago 
I realise this is a very old and closed issue, but I just wanted to confirm 
that the instructions in the FAQ don't work.

Surely this issue has always been affected by the lack of pdb multi-threading 
support, so if it worked previously them maybe there is a possibility to get it 
working now?

Original comment by andyma...@gmail.com on 8 Aug 2012 at 9:18

GoogleCodeExporter commented 9 years ago 
It seems to be working fine now. Make sure you use the remote engine.

Original comment by Pete.Do...@gmail.com on 8 Aug 2012 at 3:32

GoogleCodeExporter commented 9 years ago 
It's definitely not working for me.  I created a new Django project & app with 
a simple "Hello World" view and made sure I carefully followed each step in the 
FAQ.

As per comment 2 - it hits breakpoints in settings.py, urls.py and manage.py 
but not in views.py etc.

Pete -- can you confirm you're definitely able to hit breakpoints in views.py ?

My environment:
PyScripter 2.5.3.0 x86
Python 2.7.3 (32-bit)
Django 1.4.1
Windows 7 (64-bit)

Original comment by andyma...@gmail.com on 12 Aug 2012 at 9:04

GoogleCodeExporter commented 9 years ago 
Yes It works. Make sure your command line is runserver --noreload and make sure 
you have the latest version of rpyc http://rpyc.sourceforge.net/ installed.

The one difference is I am running on Vista on a 32bit PC.

Original comment by pete.do...@bpyfl.org on 12 Aug 2012 at 12:38

GoogleCodeExporter commented 9 years ago 
I actually didn't have rpyc installed at all - it's not mentioned anywhere as a 
requirement.

I have now installed rpyc 3.2.2 but there's no change.

Command line is definitely "runserver --noreload"

Original comment by andyma...@gmail.com on 12 Aug 2012 at 2:22