-
Couldn't load subscription status.
- Fork 30
python: EPYTEST_* related checks
#747
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
Conversation
Add a check for `EPYTEST_*` variables being declared after calling
`distutils_enable_tests`, so they don't affect it. This catches only
global scope use, as it is valid to override them in function scope.
Since using `${var:=...}` assignment is also valid, hack a quick method
to handle them as well.
Closes: pkgcore#739
Signed-off-by: Michał Górny <[email protected]>
|
Updated. |
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.
(Sorry, I didn't realise these comments were still pending and not submitted.)
| PythonAnyMismatchedDepHasVersionCheck, | ||
| PythonMissingSCMDependency, | ||
| ] | ||
| MisplacedEPyTestVar, |
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.
Nit: not a fan of "PyTest`. I think the upstream style is "pytest" but they sometimes use "Pytest". I get it's awkward because of the "E" though.
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.
Yeah, mixed feelings about that too but it seems more consistent than "Epytest" or "EPytest".
|
It looks good by the way. The comments are really just that rather than request for changes necessarily. |
Closes: pkgcore#740 Signed-off-by: Michał Górny <[email protected]>
Add a check for `EPYTEST_*` variables being declared after calling
`distutils_enable_tests`, so they don't affect it. This catches only
global scope use, as it is valid to override them in function scope.
Since using `${var:=...}` assignment is also valid, hack a quick method
to handle them as well.
Closes: #739
Signed-off-by: Michał Górny <[email protected]>
Part-of: #747
Signed-off-by: Arthur Zamarin <[email protected]>
EPYTEST_TIMEOUToverriding user value ([New Check]:EPYTEST_TIMEOUToverriding user value #740)EPYTEST_*variables ([New Check]:EPYTEST_*variables declared after callingdistutils_enable_tests#739)