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
All pytest plugins should follow the pytest_ prefix naming convention so they can be automatically included in the Pytest Plugin List.
pytest_
First, we need to figure out a suitable name for the plugin, or we can use pytest_scpdt for now as a placeholder.
pytest_scpdt
The text was updated successfully, but these errors were encountered:
Ralf's suggestion was scipy_doctest. One other suggestion (from Stefan) was doctest_sp. I actually like the latter :-). @melissawm thoughts?
scipy_doctest
doctest_sp
Sorry, something went wrong.
I like explicit names like scipy_doctest or doctest_scipy but feel free to disagree 😁
I like both scipy_doctest and doctest_scipy but shouldn't we follow the pytest naming convention? pytest_scipy_doctest?
doctest_scipy
pytest_scipy_doctest
Only if it's obligatory. IOW does not starting with pytest_ preclude the plugin discovery by pytest? Pytest is only one frontend IMO.
No, it doesn't. The only downside is that it will not be included in the pytest plugin list, which is fine.
Can we manually add it to whatever list is that?
No branches or pull requests
All pytest plugins should follow the
pytest_
prefix naming convention so they can be automatically included in the Pytest Plugin List.First, we need to figure out a suitable name for the plugin, or we can use
pytest_scpdt
for now as a placeholder.The text was updated successfully, but these errors were encountered: