Skip to content
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

Allow variance of other versions, account for dill fix #117

Merged

Conversation

oliverlockwood
Copy link
Contributor

Closes #68 (unless I've misunderstood!)

Follows on from #116.

@EntilZha, please see what you think.

@oliverlockwood oliverlockwood force-pushed the allow-other-version-variance branch from 9d6e2dd to 3cb6649 Compare November 21, 2017 12:02
@codecov-io
Copy link

codecov-io commented Nov 21, 2017

Codecov Report

Merging #117 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##           master    #117      +/-   ##
=========================================
- Coverage    99.9%   99.9%   -0.01%     
=========================================
  Files          12      12              
  Lines        2151    2149       -2     
=========================================
- Hits         2149    2147       -2     
  Misses          2       2
Impacted Files Coverage Δ
functional/test/test_functional.py 100% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 03c65ea...3cb6649. Read the comment docs.

@EntilZha
Copy link
Owner

The coverage failure seems to be a false positive from reducing number of lines so I'm merging despite that. Thanks for sorting more flexible versions out!

@EntilZha EntilZha merged commit d2ed6ba into EntilZha:master Nov 26, 2017
@oliverlockwood oliverlockwood deleted the allow-other-version-variance branch November 27, 2017 09:07
@oliverlockwood
Copy link
Contributor Author

Thanks @EntilZha!

Do you have any estimate on when these changes might be released?

@EntilZha
Copy link
Owner

I'll see if I can get travis ci setup for push-button releases today or tomorrow at which point it would be easy to release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants