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

Update launch.json schema to add "qt" #12535

Closed
int19h opened this issue Jun 24, 2020 · 3 comments
Closed

Update launch.json schema to add "qt" #12535

int19h opened this issue Jun 24, 2020 · 3 comments
Assignees
Labels
area-debugging feature-request Request for new features or functionality

Comments

@int19h
Copy link

int19h commented Jun 24, 2020

This controls whether the debugger monkey-patches PyQt/PySide to detect and trace Qt threads (microsoft/debugpy#308).

Valid values are:

  • "auto"
  • "none"
  • "pyside"
  • "pyside2"
  • "pyqt4"
  • "pyqt5"

The default is "auto", which tries to auto-detect this by import probing - this is the same as ptvsd 4 behavior.

Since that heuristic may be wrong if several different packages are installed side-by-side, the ability to specify the desired one explicitly is also provided.

"none" is provided, to give the users the ability to opt out of monkey-patching in case it breaks something.

@int19h int19h added feature-request Request for new features or functionality triage-needed Needs assignment to the proper sub-team labels Jun 24, 2020
@karthiknadig
Copy link
Member

/cc @luabud for the defaults and text.

@lucs100
Copy link

lucs100 commented Oct 25, 2023

This doesn't seem to support PyQt6 - the only way I could get breakpoints to trigger in a thread's run method was to manually add debugpy.debug_this_thread(). "pyqt6" isn't a valid value for the "qt" field; when setting "qt": "pyqt6" in my launch configs I get the error:

couldn't handle #1 request "launch" from Adapter:
             Invalid message: "qt" must be one of: ['none', 'auto', 'pyside', 'pyside2', 'pyqt4', 'pyqt5']```

@brettcannon
Copy link
Member

Due to limited resources and lack of general interest, we are unfortunately closing this issue.

@brettcannon brettcannon closed this as not planned Won't fix, can't repro, duplicate, stale Dec 18, 2023
@github-actions github-actions bot removed the needs PR Ready to be worked on label Dec 18, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-debugging feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

5 participants