Closed
Conversation
Member
Member
Author
There are no conflict merges so I don't think we need a new one. But it does need a few hours of work to get it back online. (And a few extra to make get the tests to actually pass 😄 ) |
Merged
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.
Similar to ODM2/WOFpy#65 this should be reviewed, and hopefully tested, by someone with experience
ODM2PythonAPIinternals.Currently Travis-CI is not running due to many errors that happens before the tests section. In this PR I tried to clean the configuration and the dependencies definition, which happened in multiple places, to get Travi-CI working again.
I could get to the test phase but now we have to deal with some, I beileve, genuine failures:
I also added a section for Pythons 3.4, 3.5, 3.6 and coding standards, but I marked them as expected failures because a huge effort is needed to bring those up to speed.
PS: I will take a look as AppVeyor testing in another PR.