print() doesn't work in debug console while debugging pytests

[zljubisic]

Type: Bug

If I set a breakpoint in pytest test, when I am on the breakpoint, if I enter debug console and execute prints, nothing is showed up.
Is that a bug or feature?

Extension version: 2022.14.0
VS Code version: Code 1.71.2 (74b1f979648cc44d385a2286793c226e611f59e7, 2022-09-14T21:03:37.738Z)
OS version: Windows_NT x64 10.0.19042
Modes:
Sandboxed: No
Remote OS version: Linux x64 3.10.0-1127.el7.x86_64

[fabioz]

This is a duplicate of: #19322

[zljubisic]

I am not sure that this is the same issue because I have this in settings.json, so it is not matter of defaults.

{
    "python.testing.unittestEnabled": false,
    "python.testing.pytestEnabled": true,
    "python.testing.pytestArgs": [
        "--no-cov", "-s"
    ]
}

[fabioz]

{
"python.testing.unittestEnabled": false,
"python.testing.pytestEnabled": true,
"python.testing.pytestArgs": [
"--no-cov", "-s"
]
}

Can you type in sys.argv in the Debug Console to check what are the actual args being received in your case? (i.e.: setting that works for me...).

[zljubisic]

For settings.json like:

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

I get:

00:
'/home/vagrant/.vscode-server/extensions/ms-python.python-2022.14.0/pythonFiles/testlauncher.py'
01:
'/home/vagrant/ticket...
02:
'pytest'
03:
'--rootdir'
04:
'/home/vagrant/...'
05:
'--override-ini'
06:
'junit_family=xunit1'
07:
'--junit-xml=/tmp/tmp-2214147HpdLUh2ky1.xml'
08:
'--no-cov'
09:
'--capture=no'
10:
'./tests/test_mytest.py::name of test...]'
len():
11

At the moment I can print, but from time to time print(12) just make an empty line. Do you see different vertical spaces? They are when print fails. Usually I don't have anything as output.

[fabioz]

The fact that it doesn't write sometimes due to the clipping is already reported at:

microsoft/vscode#162965

(so, this can be closed as a duplicate).

[zljubisic]

I don't know is it the same issue.
In microsoft/vscode#162965 problem is dataframe related, here the problem is with general print.
I hope that in the future I will be able to use rich print (from rich import print) to print complex object like nested dictionaries in pretty format.

[eleanorjboyd]

Hello! This is a duplicate of #19322 which just got resolved in this PR by @harupy.

[zljubisic]

Usually, end user (UAT) should confirm that problem is solved.

[eleanorjboyd]

@zljubisic, yes this is true - can someone verify?

[zljubisic]

It kind of works if you don't count occasional empty line. Please look at the space between second print and word "first".

The same goes with dictionary as well. You can see empty line that shows up occasionally.

I try to use rich print as well (from rich import print), and again, empty line (or two) show up in few 5-6 successive print executions.

[zljubisic]

I have just experienced problems with print in debug console again, so this problem is not solved:

[fabioz]

@zljubisic can you provide the debugger logs for that case?

See: https://github.com/microsoft/debugpy/wiki/Enable-debugger-logs for details on how to collect the logs.

[zljubisic]

This has happened on my business computer.
I am not sure what you are collecting and whether I am allowed to provide the logs to you. 🤔

[fabioz]

You can verify the log messages and anonymize accordingly before sending the logs.

[zljubisic]

Do you have some anonymizing function that can do that, or I have to pass over the files visually?

[zljubisic]

Do I have to put "purpose": ["debug-test", "debug-in-terminal"], in launch.json?

{
    "name": "Python: Current File",
    "type": "python",
    "request": "launch",
    "program": "${file}",
    "console": "integratedTerminal",
    "logToFile": true,
}

[fabioz]

Do you have some anonymizing function that can do that, or I have to pass over the files visually?

You need to pass them yourself and determine what's important for you to remain anonymous.

Do I have to put "purpose": ["debug-test", "debug-in-terminal"], in launch.json?

If you launch it through the testing tab or dropdown in editor yes.

[zljubisic]

@fabioz in case of vscode executed on windows 10 but connected to centos 7 in hyperv, where I should expect logs to show up?
In linux or windows?

[zljubisic]

Just to confirm that problem with print() is still present.

[fabioz]

@fabioz in case of vscode executed on windows 10 but connected to centos 7 in hyperv, where I should expect logs to show up?
In linux or windows?

It should be in Linux. I suggest you go with the environment variable in this case and point the environment variable to the place you'd like the logs to be on Linux.

p.s.: you have to do the log anonymizing manually and decide what you're comfortable sharing or not (as it's a sample case with sample code, I don't expect you to have to anonymize much...).

[eleanorjboyd]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.