Can't set the value of a variable in the debugger
已回答
I'm having trouble using the set value option in the variables window of the debugger. I'm using PyCharm 2017.3.3 (Professional Edition) (Build #PY-173.4301.16, built on January 11, 2018) on Windows 10 Enterprise. I have a simple dictionary and want to change the value of one of the elements. There is no nastygram - the value just reverts back to the original value. This seems related to this post but it was quite a while ago. Perhaps it broke again??
A colleague clued me in to the fact that I can do assignment inside the evaluate window! I had been using that to look at expressions but never imagined I could do an assignment! So I can do what I want another way but I don't understand why set value is not working for me.
请先登录再写评论。
Here's a screen shot of the thing I was trying to do (doesn't work):
The alternative method (which works):
Hi Jpfuntne! It looks like a bug (or a missing feature), I created the corresponding ticket in the bug tracker: https://youtrack.jetbrains.com/issue/PY-28563
This problem still happens in Pycharm 2019.1 !
Jean-Pierre
This is happening for me in 2019.2, as well
2019.2.3 same issue, just started happening
Hello!
The bug has not been fixed yet, please feel free to vote for it in order to increase its priority https://youtrack.jetbrains.com/issue/PY-28563?_ga=2.114365572.2053364720.1569749179-1726696482.1567521918
PyCharm 2019.2.5 (Professional Edition)
still have this problem
pycharm 2019.2.5 (community edition) also has this problem
This issue still exist even with Ultimate Edition. Set value option is still greyed out.
Please help in fixing this issue.
Rider 2020.1.4 (ubuntu 20.04)
setValue for a normal variable within debugging session does not work
Is this actually still a problem in the pro version in August of 2020? It looks like it? Maybe I'm just missing soemtihng though?
Unfortunately the problem still exists...
I meet the same problem in pro version 2020.3.
This is a big problem for me. I often use boolean assignments used in conditional execution during debugging sessions to execute otherwise difficult-to-trigger behavior.
Problem still here. Any news on when this will be fixed?
I need this fixed! Indispensable feature to have. Why is it still an issue?