Default to --capture=no when debugging pytest

Pavel Minaev (@int19h)

From the discussion on StackOverflow, this is due to microsoft/debugpy#899 (comment). So it seems that VSCode should default to --capture=no when debugging pytest.

Originally posted by Pavel Minaev (@int19h) in microsoft/debugpy#947 (comment)

Karthik Nadig (@karthiknadig)

Karthik Nadig (@karthiknadig) Can I work on this issue?

Harutaka Kawamura (@harupy)

Harutaka Kawamura (@harupy) go ahead.

I don't know why we need default to --capture=no, because if we set it in settings.json:

{
    "python.testing.pytestArgs": [
        "tests",
        "--no-cov",
        "--capture=no"
    ],
    "python.testing.unittestEnabled": false,
    "python.testing.pytestEnabled": true,
    "testing.defaultGutterClickAction": "debug"
}

even you can see it as a command option in sys.argv --capture=no is not used.

We could say the same for --no-cov because coverage steals tracing api (sys.settrace), so if we are debugging turn of the coverage.

Default to `--capture=no` when debugging pytest (#19903)

How about --no-cov?

started new issue for the --no-cov feature request here: #19985

Thanks

Default to `--capture=no` when debugging pytest (microsoft/vscode-pyt…

Navigation Menu

Repository navigation

Default to `--capture=no` when debugging pytest #19322

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Default to --capture=no when debugging pytest #19322

Description

Activity

harupy commented on Sep 24, 2022

karthiknadig commented on Sep 27, 2022

zljubisic commented on Oct 10, 2022

zljubisic commented on Oct 10, 2022

eleanorjboyd commented on Oct 11, 2022

zljubisic commented on Oct 11, 2022

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Default to `--capture=no` when debugging pytest #19322