BUG: can't discover pytest tests because of ValueError: sourece code string cannot contain null bytes

[tigerhawkvok]

Reporting in this format because of #19787

[ERROR 2022-8-6 10:12:23.977]: Error discovering pytest tests:
 n [Error]: Traceback (most recent call last):
  File "c:\Users\pkahn\.vscode\extensions\ms-python.python-2022.14.0\pythonFiles\testing_tools\run_adapter.py", line 17, in <module>
    from testing_tools.adapter.__main__ import parse_args, main
ValueError: source code string cannot contain null bytes

    at ChildProcess.<anonymous> (c:\Users\pkahn\.vscode\extensions\ms-python.python-2022.14.0\out\client\extension.js:2:240364)
    at Object.onceWrapper (node:events:646:26)
    at ChildProcess.emit (node:events:526:28)
    at maybeClose (node:internal/child_process:1092:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)

for extension

Name: Python
Id: ms-python.python
Description: IntelliSense (Pylance), Linting, Debugging (multi-threaded, remote), Jupyter Notebooks, code formatting, refactoring, unit tests, and more.
Version: 2022.14.0
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-python.python

[karthiknadig]

@tigerhawkvok Wat is the version of python you are using? Also, can you share the entire log from Output > Python?

[karthiknadig]

Can you also try this, it might be that you have a corrupt update:

1. Uninstall Python extension (if you have pylance uninstall it first).
2. Close all instances of VS Code.
3. Go to, %USERPROFILE%/.vscode/extensions (on windows) or ~/.vscode/extensions on Linux/Mac.
4. Delete any folder with the name starting with ms-python.python*
5. Start VS Code, and install Python extension (also pylance if you uninstalled it in step 1).

[tigerhawkvok]

I'll try that tomorrow afternoon PDT, it's on my work machine.

[eleanorjboyd]

Hello @tigerhawkvok! I just wanted to follow up to see if you got a chance to try @karthiknadig suggestion he posted on Sep 7th. Additionally if this problem is fixed we can go ahead and close the issue. Thanks!

[brettcannon]

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.