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

Migrate to pyproject.toml #1131

Merged
merged 2 commits into from
Aug 31, 2023
Merged

Migrate to pyproject.toml #1131

merged 2 commits into from
Aug 31, 2023

Conversation

Spitfire1900
Copy link
Contributor

Migrate away from setuptools to pyproject.toml

Attanched output of diff --recursive --unified .venv-setup.py/ .venv-pyproject.toml/ | grep -v 'Binary files' > venv.diff

venv.diff.txt

@Spitfire1900 Spitfire1900 mentioned this pull request Aug 31, 2023
@Spitfire1900
Copy link
Contributor Author

Testing shows that this closes #1121

@bwendling bwendling merged commit dd89b23 into google:main Aug 31, 2023
@Spitfire1900 Spitfire1900 deleted the pyproject.toml branch August 31, 2023 22:30
bwendling pushed a commit that referenced this pull request Oct 10, 2023
So while migrating to pyproject.toml fixed editable installation behavior on Ubuntu,
Pylance was still unable to figure out imports as vscode does not understand the
import script .venv/lib/python3.10/site-packages/__editable___yapf_0_40_2_finder.py
created by an editable install triggered by pip install -m venv .venv

Using https://microsoft.github.io/pyright/#/import-resolution?id=setuptools
suggestions of compat and strict mode did not resolve issues either.

So instead I revert to manually adding third_party to the python.analysis.extraPaths
setting in settings.json
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

Successfully merging this pull request may close these issues.

2 participants