-
Notifications
You must be signed in to change notification settings - Fork 8
Fixes for julia 0.7/1.0 #32
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #32 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 2 2
Lines 61 63 +2
=====================================
+ Hits 61 63 +2
Continue to review full report at Codecov.
|
Thanks for the contribution! Do you know if the 0.5 failures are known issues — perhaps something generic related to running Julia in Travis? I don't think it should have become a problem without any changes in the actual code... |
Sure! I'm not sure about the 0.5 errors and didn't dig into it very much. I asked at the upgradathon if maintaining compatibility with old versions of Julia was a goal, and Simon B. said not really because users of old versions of Julia would still be handed the old version of the library. But if its a goal for Tau.jl to be compatible with 0.5, I can look into it some more. |
Nah, it's not a big deal. I would just have preferred if it could be avoided easily. The error seems pretty generic, so I believe it's possible that many of the packages aiming to maintain 0.5 compatibility (arguably not that many anyway) would be facing this issue. If it turned out to be something someone already knew how to fix, that'd be ideal. Otherwise, I wouldn't bother digging into it. On a separate note, do you think you could integrate the changes to appveyor.yml I introduced in #30? Or would you prefer to have this PR merged this first, and we'd make that change afterwards? |
I don't mind integrating the appveyor changes at all. It's up to you if we do it as part of this PR. I'll try to do that in the next day or two--if this PR isn't merged by the time I get to it, then I'll cherry-pick that work and merge it here. |
I think it makes sense to do those changes as part of this PR. Feel free to integrate them at your leisure :) |
I just integrated the |
Thanks for doing that, and sorry I didn't get to it as quickly as I thought I would. |
No worries, you did the bulk of the work on this PR -- it was only fair that someone else do the work of integrating changes made elsewhere ;) |
No description provided.