Pycharm 2.7 can't debug

Permanently deleted user

Created February 10, 2013 23:49

I can't use pycharm 2.7 to debug django project anymore. But the same project can debug using 2.6.

I add PYCHARM_DEBUG to environment variables and get a lot of message like below. Please help me.

sending cmd: CMD_SIGNATURE_CALL_TRACE 130    4094    <xml><call_signature file="/Users/wanyi/Developer/python_ve/django/lib/python2.7/sre_parse.py" name="Tokenizer.__next"><arg name="self" type="sre_parse.Tokenizer"></arg></call_signature></xml>

sending cmd: CMD_SIGNATURE_CALL_TRACE 130    4096    <xml><call_signature file="/Users/wanyi/Developer/python_ve/django/lib/python2.7/sre_parse.py" name="SubPattern.__len__"><arg name="self" type="sre_parse.SubPattern"></arg></call_signature></xml>

sending cmd: CMD_SIGNATURE_CALL_TRACE 130    4098    <xml><call_signature file="/Users/wanyi/Developer/python_ve/django/lib/python2.7/sre_parse.py" name="SubPattern.__len__"><arg name="self" type="sre_parse.SubPattern"></arg></call_signature></xml>

sending cmd: CMD_SIGNATURE_CALL_TRACE 130    4100    <xml><call_signature file="/Users/wanyi/Developer/python_ve/django/lib/python2.7/sre_parse.py" name="SubPattern.__getitem__"><arg name="self" type="sre_parse.SubPattern"></arg><arg name="index" type="__builtin__.slice"></arg></call_signature></xml>

sending cmd: CMD_SIGNATURE_CALL_TRACE 130    4102    <xml><call_signature file="/Users/wanyi/Developer/python_ve/django/lib/python2.7/sre_parse.py" name="SubPattern.__init__"><arg name="self" type="sre_parse.SubPattern"></arg><arg name="pattern" type="sre_parse.Pattern"></arg><arg name="data" type="__builtin__.list"></arg></call_signature></xml>

sending cmd: CMD_SIGNATURE_CALL_TRACE 130    4104    <xml><call_signature file="/Users/wanyi/Developer/python_ve/django/lib/python2.7/sre_parse.py" name="SubPattern.__len__"><arg name="self" type="sre_parse.SubPattern"></arg></call_signature></xml>

sending cmd: CMD_SIGNATURE_CALL_TRACE 130    4106    <xml><call_signature file="/Users/wanyi/Developer/python_ve/django/lib/python2.7/sre_parse.py" name="SubPattern.__len__"><arg name="self" type="sre_parse.SubPattern"></arg></call_signature></xml>

sending cmd: CMD_SIGNATURE_CALL_TRACE 130    4108    <xml><call_signature file="/Users/wanyi/Developer/python_ve/django/lib/python2.7/sre_parse.py" name="SubPattern.__getitem__"><arg name="self" type="sre_parse.SubPattern"></arg><arg name="index" type="__builtin__.int"></arg></call_signature></xml>

6 comments

Permanently deleted user

Created February 11, 2013 01:07

I found out the reason cause my problem. The python debugger option "Collect run-time types information for code insight" is the cause. Turning it off can make my django project to be able to debug again.

Anyone call tell me why this option can't be used in django?

Permanently deleted user

Created February 11, 2013 12:18

Hi Wan! What was exactly the problem with debugging your Django project?

Permanently deleted user

Created February 11, 2013 12:24

sorry for my poor english.

My problem is that Pycharm 2.7 can't debug my Django project when I turn on the "Collect run-time types information for code insight" option.

Pycharm will wait for a long time and start the test server. But I can't open the page in the browser.

Permanently deleted user

Created February 11, 2013 12:45

I've created an issue: http://youtrack.jetbrains.com/issue/PY-8844

Permanently deleted user

Created February 11, 2013 13:09

Thank you.

Permanently deleted user

Created March 01, 2013 01:15

I updated to Pycharm 2.7.1, it still can't debug Django app when "Collect run time types information for code insight" option turns on.

Please sign in to leave a comment.