This means that the every file needs to be re-associated for every debugging session something is clearly wrong. Unfortunately, the association does NOT remain in P圜harm across debugging sessions. I do not know why invalidate caches on its own did not solve the issue. I believe the problem was that a previous version of P圜harm had associated that path file with a cached old version of the library. I arbitrarily chose the latter one, and subsequently, debugging line numbers appeared to match up for that file. Also, the number of bytes and the modification times were the same in each file: pnore at pnore-mbp in ~/Library/Caches I did a diff between the two that were available, and there was no difference. I clicked auto-detect and noticed that two versions were available: The next time I tried debugging the same file, I was given a screen to select the sources. I thought I had solved this issue by removing all of the ~/Library/Caches/P圜harmXX/remote_sources/* files, re-invalidating the caches, restarting P圜harm, and re-associating the remote interpreter with the project. I have also tried File > Invalidate Caches / Restart and in this particular case neither have helped. My question is: how can I correct this behavior? I have tried blowing away my virtualenv and then rebuilding it and reassociating it with P圜harm. The left sidebar will now show you a tree structure with all the files in your project. P圜harm will create a new project and open it. This is not the first time I have seen this in P圜harm while viewing the library source usually works, occasionally I will see a mismatch between the source caches and what is being executed. All you need to do to create your Flask project is to start P圜harm, select Open, and then choose the top-level directory of your application. Also, note how the breakpoint is clearly on a docstring: Here's another example that shows how variables in scope in the debugger don't match the single variable passed in. ![]() When I step through the DRF code with the debugger on, I can see that it is stepping through blank lines, and the variables in the debugger don't match those in scope (pictured here is rest_content()): ![]() Incidentally, I have P圜harm configured to use a virtualenv inside a local vagrant box. I'm using Django Rest Framework 3.5.4 and Pycharm Professional 2016.3.1.
0 Comments
Leave a Reply. |