-
Notifications
You must be signed in to change notification settings - Fork 42
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
chore: Remove requirement for pytest #273
Conversation
pytest was required only by the `PythonStandardRunner`, and only in the `strict_mode`. No one uses that. At first it was develop because we were concerned that users would be picky by us running pytest with `subprocess.run`, so `strict_mode` was an alternative. Since then people are starting to use ATS and that hasn't been an issue. Plus with custom runners we can solve this problem without the complications of requiring pytest. And there's a possibility (although I think it's very unlikely) that importing pytest from the CLI might cause some of the issues we were seeing when running tests from it in ATS. Who knows. In any case, removing pytest and all code associated with it.
c0b48b7
to
d8b0850
Compare
Codecov Report
@@ Coverage Diff @@
## master #273 +/- ##
==========================================
- Coverage 94.91% 94.86% -0.05%
==========================================
Files 78 78
Lines 2694 2631 -63
==========================================
- Hits 2557 2496 -61
+ Misses 137 135 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
can _wait_pytest
and the imports for Process
and Queue
be removed form python_standard_runner
be removed as well? Otherwise, lgtm!
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.
other than my previous comment, lgtm!
pytest was required only by the
PythonStandardRunner
, and only in thestrict_mode
.No one uses that.
At first it was develop because we were concerned that users would be picky by us running pytest with
subprocess.run
,so
strict_mode
was an alternative. Since then people are starting to use ATS and that hasn't been an issue.Plus with custom runners we can solve this problem without the complications of requiring pytest.
And there's a possibility (although I think it's very unlikely) that importing pytest from the CLI
might cause some of the issues we were seeing when running tests from it in ATS. Who knows.
In any case, removing pytest and all code associated with it.