Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
skip get_requires for setuptools projects #41
skip get_requires for setuptools projects #41
Changes from 18 commits
873180f
7a80716
7dfd8f4
ceefb83
d801116
054c77c
b67f4d3
927b3af
fa9adcb
aa2049b
23ce5e1
e5c8b5e
6fa35e0
3a7d2a1
1a5f6f8
b265072
fdd491b
a0c371a
43d5b00
439053b
1c7c9e5
a564484
4c4763b
61fed2f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Not a big deal, but this parametrization is hard to read. You might consider doing something like creating a list of multiline strings or something and then using
zip(contents, errors)
instead.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 you're right. I just tried reformatting it by removing "should this raise an error?" from the parameterization completely and splitting it into 2 tests (one with cases that shouldn't result in an error, one with cases that should).
I think it's a lot easier to read and understand now:
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.
The three new tests are similar enough that I suspect you could convert them to a single parametrized test fairly easily, but I could be wrong.
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.
I think the sets of assertions are different enough, and the setup before that small enough, to justify separate test cases.
They could get put into one parameterized test but that test would end like this:
I think it's a little easier to follow the logic by keeping these new tests as separate cases.