You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 1, 2024. It is now read-only.
Pytest-benchmark would be most convenient, but pytest tries really hard to do path magic, and as such always finds the local source before anything installed in site-packages, even if you haven't done a setup.py develop. This means that you can't use pytest's runner to do any tests or benchmarks against an optimized build.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Some discussion in #55
Pytest-benchmark would be most convenient, but pytest tries really hard to do path magic, and as such always finds the local source before anything installed in site-packages, even if you haven't done a
setup.py develop
. This means that you can't use pytest's runner to do any tests or benchmarks against an optimized build.The text was updated successfully, but these errors were encountered: