Skip to content
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

Arguments tab defaults to collapsed when debugging #49

Closed
AdamBJ opened this issue Nov 11, 2017 · 2 comments
Closed

Arguments tab defaults to collapsed when debugging #49

AdamBJ opened this issue Nov 11, 2017 · 2 comments
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster

Comments

@AdamBJ
Copy link

AdamBJ commented Nov 11, 2017

I'm not %100 sure if this is the place for this issue. However, I don't think it's a general issue with VS Code because of what was said in this issue.

Environment data

VS Code version: 1.17.2
Python Extension version: 0.7.0
Python Version: 3.6.2
OS and version: Windows 10 Home, 1703

Actual behavior

When debugging, the "Arguments" tab inside VARIABLES defaults to closed.
image

Expected behavior

Arguments are pretty important, perhaps this should default to open, like it does for local variables? Or at least have an option to toggle this behaviour.

Steps to reproduce:

Debug any Python program

Logs

Output from Python output panel

Output from Console window (Help->Developer Tools menu)

image

@DonJayamanne
Copy link

@AdamBJ
Apologies for the late response. We've been working on a new Python debugger.
Please could you test this issue with the new experimental debugger in the latest version of the extension.

Open your existing .vscode/launch.json and change the setting "type":"python" to "type":"pythonExperimental"

Note: The Arguments tab will not be available, however we do have other tabs such as Variables.

@DonJayamanne DonJayamanne added info-needed Issue requires more information from poster upstream-ptvsd-old and removed needs PR labels May 31, 2018
@no-response no-response bot closed this as completed Jun 28, 2018
@no-response
Copy link

no-response bot commented Jun 28, 2018

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants