We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When Salvus is imported during the import of hmc_tomography, a message is displayed showing the status of the license, e.g. here: https://github.com/larsgeb/hmc-tomography/blob/21d2bb322b7da31457b3f0ae211972db3f211391/hmc_tomography/Distributions/__init__.py#L31 VSCode's way of discovering tests is to run Pytest's discover and parse its output. This gets mixed with the Salvus output and subsequently fails with a JSON error.
hmc_tomography
This is also a bad design choice of VSCode. Other people encounter these issues too: microsoft/vscode-python#11729.
The text was updated successfully, but these errors were encountered:
larsgeb
No branches or pull requests
When Salvus is imported during the import of
hmc_tomography
, a message is displayed showing the status of the license, e.g. here:https://github.com/larsgeb/hmc-tomography/blob/21d2bb322b7da31457b3f0ae211972db3f211391/hmc_tomography/Distributions/__init__.py#L31
VSCode's way of discovering tests is to run Pytest's discover and parse its output. This gets mixed with the Salvus output and subsequently fails with a JSON error.
This is also a bad design choice of VSCode. Other people encounter these issues too: microsoft/vscode-python#11729.
The text was updated successfully, but these errors were encountered: