-
Notifications
You must be signed in to change notification settings - Fork 293
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
Bug: The variable explorer doesn't show the shape of np arrays in the "count" column #2093
Comments
nevermind, just looked through our previous issues. It's a duplicate of microsoft/vscode-python#10140. The explanation for why we can only show one dimension is below: "We switched computing the value of the variable to use the jupyter ? command instead of running python code. This output doesn't seem to include the shape for ndarrays. We did this so we could start supporting other kernels besides python." |
Thank you for your fast answer. If its not a bug then see it as a feature request ;) In my opinion the "count" column is quite meaningless for numpy arrays and maybe also confusing in the current state. |
While this is a regression, it's not quite meeting the bar for must fix at this time. |
I think this feature is really important for many data scientists. |
Bug: The variable explorer doesn't show the shape of np arrays in the "count" column
Steps to cause the bug to occur
Actual behavior
The "count" column shows only the number of rows I assume.
Expected behavior
I saw in a YouTube video that the "count" column should actually show the shape (
x.shape
)I use a lot of linear algebra calculations with multi-dimensional arrays, so for me it is quite important to see the shape of an array at a glance. Workaround for me is using the iPython REPL to get the shape, which is clunky.
Your Jupyter and/or Python environment
Please provide as much info as you readily know
Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer
The text was updated successfully, but these errors were encountered: