10 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Marcio Mazza	c243608ac6	Add your name to AUTHORS.txt	2022-09-05 17:31:14 -03:00
Marcio Mazza	e25750ecef	Make code compatible with python < 3.8	2022-09-05 17:05:11 -03:00
Marcio Mazza	1a306fddbf	Fix check pytest fixture from import on the right context	2022-09-04 13:12:13 -03:00
Marcio Mazza	ec425ed2af	Add tests to find pytest fixtures from external plugins	2022-09-03 17:16:32 -03:00
Marcio Mazza	fa1e9ce9a7	Simplify entry points enumeration	2022-09-03 17:16:32 -03:00
Marcio Mazza	8447d7f3e4	Discard imports of modules as pytest fixtures	2022-09-03 17:16:32 -03:00
Marcio Mazza	27e13e4072	Allow for multiple returns from goto_import	2022-09-03 17:16:32 -03:00
Marcio Mazza	9fd4aab5da	Find pytest fixtures from external plugins registered via setuptools entry points ... Using setuptools entry points is probably the main pytest mechanism of plugin discovery. See https://docs.pytest.org/en/stable/how-to/writing_plugins.html#setuptools-entry-points This extends the functionality of #791 and maybe eliminates the need for #1786.	2022-09-03 17:16:32 -03:00
Marcio Mazza	fa0c064841	Fix skipped collection of pytest integration test files ... On integration tests file collection, the value of `environment.executable` can also be a symlink (e.g. in a virtualenv) with a different name than, but pointing to the same as `sys.executable` (e.g. .../bin/python3.10 and .../bin/python, respectively). That causes skipping the collection of `completion/pytest.py` and `completion/conftest.py` a lot of times, depending on the environment. (e.g. "60 skipped" before x "23 skipped" after, in a local virtualenv)	2022-09-02 14:23:38 -03:00
Marcio Mazza	85c7f14562	Fix test where home could be a potential project	2022-09-01 13:01:27 -03:00