-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display order of properties of a tensor object in debugging #1525
Comments
We don't officially support this, but I believe you could author a pydevd extension to customize the representation for your type - have a look at https://github.com/microsoft/debugpy/tree/main/src/debugpy/_vendored/pydevd/pydevd_plugins/extensions. Note however that we will be moving away from pydevd in the future. However, given that ML/AI is a particularly important scenario these days, I'd love to hear more about the nature of customizations in question, so that we can properly address this in our new debugger. |
The shape(dimension) of a tensor in vscode is far away from the top. Frequent need to expand and view results in low efficiency. And pycharm can see the type and shape without opening the variable, as shown in the figure. We are very concerned about the dimensions of tensors in ML/AI, it's so convenient. |
I believe the following issue are all about the same thing. The shape of numpy and tensor is so important for debuger in ML/AI. #1191 |
The shape of a variable cannot be easily viewed.Whether mouse hover will be supported in the future to see the shape of the variable. |
It is obvious that everyone is very satisfied with the debugging of pycharm. If there are no patents or other restrictions, you can copy the display stype and information of pycharm. If there are restrictions, ignore my comments pls. |
In addition to tensor and numpy, pycharm also has good type display support for list, tuple, dict, etc. |
I tempory use this but I strongly suggest vscode to support it natively |
Can I adjust the display order of properties of a tensor object when debugging Python in vscode? Because in deep learning, we focus more on the shape of a tensor rather than specific values. Now we want to see the value of a tensor by pulling it down a long distance. This has reduced my debugging efficiency.
The text was updated successfully, but these errors were encountered: