python console not loading on 2017.1

Answered

Updated PyCharm, python console seems to completely not load - just a grey box, with no buttons or anything.. Suggestions?

8 comments
Comment actions Permalink

I updated to 2017.1 yesterday and my Python Console is working, but the console in the debugger is failing strangely.  It shows the output I am used to seeing when stopping at a breakpoint, but then does nothing in response to anything I enter at the prompt.  That said, the Debugger tab is showing all of the correct variables and the Evaluate Expression panel is working.  

Maybe these issues are related.

I submitted issue: PY-23398

1
Comment actions Permalink

Hi,Michele Ciccozzi! Could you please provide your log folder from (Help | Show log in Files).

0
Comment actions Permalink

Hi Eric Bergerson! Yes, unfortunately, it's a known problem that debug console doesn't work when debugging tests. We're working on it.

0
Comment actions Permalink

So the error that should to be causing my issue, as per the log file, seems to be an IndexNotReadyException, which is weird because I waited for the indexing processes to complete before doing anything.

I will try again and report back; in the meantime, I'd suggest giving the users a slightly better feedback than a grey rectangle where a familiar interface used to consistently be.

0
Comment actions Permalink

So as a promised follow-up, I looked very carefully today when I updated to the RC2: I noticed that indeed there's absolutely no feedback that the indexing process is not done, but the console still refuses to load during the initial launch. It loads fine if I wait a bit (again, an undefined amount of time) and then relaunch the whole app.

0
Comment actions Permalink

Michele Ciccozzi Could you please create an issue in our issue tracker https://youtrack.jetbrains.com/issues/PY and provide the contents of your log folder? Thank you!

0
Comment actions Permalink

I'm getting this same issue in 2017.3 when running PyTest selenium scripts. The debug console is unresponsive when it stops at a break point. The bug entry https://youtrack.jetbrains.com/issue/PY-23398 says this is a duplicate of https://youtrack.jetbrains.com/issue/PY-24875 (which is supposed to be fixed). But it doesn't seem to be the same thing. Although I do have the teamcity plugin running, I don't seem a whole bunch of teamcity output as reported and I do have an unresponsive console. 

 

My project uses

- Pytest

- Virtual environment (python 3.5.3)

- Teamcity plugin

- Pycharm 2017.3

 

0
Comment actions Permalink

Hi! We still suggest using a workaround for pytest runners from this comment: https://youtrack.jetbrains.com/issue/PY-22505#comment=27-2117507

0

Please sign in to leave a comment.