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

Automatically connect to avoid reportMissingModuleSource Pylance #1418

Open
s-smits opened this issue Oct 20, 2024 · 0 comments
Open

Automatically connect to avoid reportMissingModuleSource Pylance #1418

s-smits opened this issue Oct 20, 2024 · 0 comments

Comments

@s-smits
Copy link

s-smits commented Oct 20, 2024

[{
	"resource": "/Users/air/Developer/Projects/../src/.../extract.py",
	"owner": "_generated_diagnostic_collection_name_#6",
	"code": {
		"value": "reportMissingModuleSource",
		"target": {
			"$mid": 1,
			"path": "/microsoft/pyright/blob/main/docs/configuration.md",
			"scheme": "https",
			"authority": "github.com",
			"fragment": "reportMissingModuleSource"
		}
	},
	"severity": 4,
	"message": "Import \"pandas\" could not be resolved from source",
	"source": "Pylance",
	"startLineNumber": 2,
	"startColumn": 8,
	"endLineNumber": 2,
	"endColumn": 14
}]

Screenshot 2024-10-20 at 16 20 35

How to easily prevent these warnings? It'd pretty complex to dynamically assign the libraries to Pylance based on .venv that's created (at least I don't know how this can be done especially dynamically). If this could be done automatically it'd save me a lot of warnings!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant