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
Try to weed out "Framework :: Pytest" false-positives #53
Comments
I've been thinking about this recently as well - but I'm not sure what we can do, other than a hand-written list of exceptions? FWIW I've tried to track down some of the repos and submit a PR, but many of those don't seem to exist, so I only ended up with https://github.com/BotEX-Developers/botbase/pull/12. |
Yeah I'm not sure either, but a thought that occurred was: For all packages that don't start with "pytest-" and declare Of course there are obvious drawbacks: false positives, manual parsing is tricky/might be flaky, etc., but in the end we might get better results than what we are having currently. |
The number of false positivies is too large, only list pytest-* plugins for now until a final solution to pytest-dev#53 is implemented.
until pytest-dev#53 is resolved. See pytest-dev#55
Closed by #66. |
It seems a lot of packages are using the
Framework :: Pytest
classifier even though they are not plugins, but only use pytest to test their own code. This generates a bunch of false positives that we should avoid showing.The text was updated successfully, but these errors were encountered: