Add numpy+jsonschema to env + drop Python 3.6 in CI (use 3.7 instead)
#151
Conversation
This file contains 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
3 tasks
dominiquesydow
changed the title
numpy version conflicts with mdanalysisnumpy to env + drop Python 3.6 in CI (use 3.7 instead)
dominiquesydow
changed the title
numpy to env + drop Python 3.6 in CI (use 3.7 instead)numpy+jsonschema to env + drop Python 3.6 in CI (use 3.7 instead)
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.
Description
See issue: #150
Todos
numpyversion conflicts withmdanalysis: Addnumpytotest_env.ymljsonschemaversion shipped withbravado(<4.0.0) comes without a necessary module, thus manually installjsonschema<4.0.0 here until this is fixed in bravado/swagger_spec_validator or else - REVISIT THIS Opened issue as a reminder: Reminder: Removejsonschemafrom environments #152numpyversion conflicts withmdanalysis#150"Questions
None
Status