Repository navigation
pytest 3 settings - #21
Merged
Merged
Conversation
Owner
|
Before I merge this, does |
Owner
|
@pllim - actually, not sure you automatically get notifications, so just to be sure, do you know that |
Author
|
Ops... My reply is a bit too late. But at least on Appveyor log, I see that it installed pytest 3 but then used bundled pytest 2 anyway. I guess we'll see... |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This forces Appveyor and Travis to use system pytest, which presumably will be pytest 3 (untested). Also fixes pytest warnings that I reported.
NOTE: Not sure how to enforce pytest 3 in CircleCI but I don't really care about that one.