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

visualstudio_py_testlauncher.py - format_exception() missing 3 required positional arguments: 'etype', 'value', and 'tb' #3305

Closed
Ark-kun opened this issue Nov 12, 2018 · 4 comments
Labels
area-testing bug Issue identified by VS Code Team member as probable bug

Comments

@Ark-kun
Copy link

Ark-kun commented Nov 12, 2018

I got an exception while trying to debug a unittest. The exception was from a bug in VSCode Python extension itself:

Exception has occurred: TypeError
format_exception() missing 3 required positional arguments: 'etype', 'value', and 'tb'
  File "C:\Users\Ark\.vscode\extensions\ms-python.python-2018.9.2\pythonFiles\PythonTools\visualstudio_py_testlauncher.py", line 344, in main
    pass
  File "C:\Users\Ark\.vscode\extensions\ms-python.python-2018.9.2\pythonFiles\PythonTools\visualstudio_py_testlauncher.py", line 347, in <module>
    main()

I looked at the extension's code and the error is correct. See DonJayamanne@3e50a68#r31258938

Environment data

  • VS Code version: 1.28.2
  • Extension version: 2018-10-01
  • OS and version: Windows 10
  • Python version: 3.7.0 x64
  • Type of virtual environment used: N/A

Actual behavior

Exception has occurred: TypeError
format_exception() missing 3 required positional arguments: 'etype', 'value', and 'tb'
  File "C:\Users\Ark\.vscode\extensions\ms-python.python-2018.9.2\pythonFiles\PythonTools\visualstudio_py_testlauncher.py", line 344, in main
    pass
  File "C:\Users\Ark\.vscode\extensions\ms-python.python-2018.9.2\pythonFiles\PythonTools\visualstudio_py_testlauncher.py", line 347, in <module>
    main()

Expected behavior

No exception

@DonJayamanne DonJayamanne added bug Issue identified by VS Code Team member as probable bug needs PR area-testing labels Nov 12, 2018
@VCPintoHUUB
Copy link

Hi,
Any workaround for this bug?
Will it be fixed?

@VCPintoHUUB
Copy link

Hi,
Any hope on seeing this fixed?

@brettcannon
Copy link
Member

We are going through old issues and we noticed that no one had replied to this issue. I want to apologize for the oversight and to let you know that the issue was triaged (as shown by the labels applied to this issue).

@github-actions github-actions bot removed the needs PR label Aug 9, 2022
@karrtikr karrtikr added the needs PR Ready to be worked on label Aug 9, 2022
@eleanorjboyd
Copy link
Member

Hello! I have reviewed this issue and given the architectural changes of the testing rewrite, this issue should no longer exist on the rewrite. Therefore I am going to close this issue but please comment or open a new issue if you are still seeing a problem when you try this yourself!

To use the rewrite yourself just add ”python.experiments.optInto": ["pythonTestAdapter"] to your user settings. You can confirm you have the rewrite enabled by setting your log level to trace, via the Developer: Set Log Level command in the command palette. Then check to see if Experiment 'pythonTestAdapter' is active is in your python logs.

Thanks!

@github-actions github-actions bot removed the needs PR Ready to be worked on label Oct 30, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-testing bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

7 participants