-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Pytest plugin cherrypick #20175
Pytest plugin cherrypick #20175
Conversation
…19828) For microsoft#19101 Before the change item events start coming in, we have to ensure quickpick is ready to receive those events.
…nent (microsoft#19827) Ensure we start watchers and create workspace related objects when activating discovery component
Done temporarily on request of Pylance so they can begin testing.
pythonFiles/pytest-vscode-integration/pytest_vscode_integration.egg-info/SOURCES.txt
Outdated
Show resolved
Hide resolved
pythonFiles/pytest-vscode-integration/tests/test_vscode_integration.py
Outdated
Show resolved
Hide resolved
pythonFiles/pytest-vscode-integration/tests/test_vscode_integration.py
Outdated
Show resolved
Hide resolved
pythonFiles/pytest-vscode-integration/tests/test_vscode_integration.py
Outdated
Show resolved
Hide resolved
pythonFiles/pytest-vscode-integration/tests/test_vscode_integration.py
Outdated
Show resolved
Hide resolved
pythonFiles/pytest-vscode-integration/tests/test_vscode_integration.py
Outdated
Show resolved
Hide resolved
pythonFiles/pytest-vscode-integration/tests/test_vscode_integration.py
Outdated
Show resolved
Hide resolved
…ation.py Co-authored-by: Brett Cannon <brett@python.org>
…ation.py Co-authored-by: Brett Cannon <brett@python.org>
…ation.py Co-authored-by: Brett Cannon <brett@python.org>
…ation.py Co-authored-by: Brett Cannon <brett@python.org>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There should be no .egg-info
directory in the repo (or anywhere). That's really old setuptools stuff. If we have to have an entry_points.txt
file then it should be in a .dist-info
directory for the code. In fact there should be no use of setuptools in our repo as it's too heavy-handed for what we need it for. We should be using flit_core or hatchling as a build back-end instead since we only have pure Python packages. I.e. no setup.py
, only pyproject.toml
.
Have you tried using the -p
option with the directory containing the plug-in on PYTHONPATH
(or some other way to get it on to sys.path
)? The wording of https://docs.pytest.org/en/stable/how-to/writing_plugins.html#making-your-plugin-installable-by-others suggests it might not be necessary to define an entry point. It also has an example of how to use pyproject.toml
and hatchling to package things up if it turns out we actually do have to provide an entry point.
closing in favor of #20566 |
Fixes #20077