Skip to content

Suggestion: Change config name to start with "Debugpy" instead of "Python" when using automatically generated configs #39

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

Closed
luabud opened this issue Jun 27, 2023 · 0 comments · Fixed by #47
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@luabud
Copy link
Member

luabud commented Jun 27, 2023

Testing #36

This is a suggestion for consistency. When you create a debug config in launch.json for Debugpy, the config names have Debugpy with a prefix instead of Python, which I like:
image

But when using automatic configurations, the configs show up with a "Python" prefix, which can be confusing if you also open automatic configs generated by the Python extension, as the entries are duplicated:

image

If we could rename the ones generated by Debugpy to start with Debugpy, I think it would be better.

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Jun 27, 2023
@paulacamargo25 paulacamargo25 added bug Issue identified by VS Code Team member as probable bug and removed triage-needed Needs assignment to the proper sub-team labels Jun 27, 2023
@paulacamargo25 paulacamargo25 added this to the June 2023 milestone Jun 29, 2023
@amunger amunger added the verified Verification succeeded label Jun 29, 2023
@rzhao271 rzhao271 added verified Verification succeeded and removed verified Verification succeeded labels Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants