-
Notifications
You must be signed in to change notification settings - Fork 250
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
WIP: update for julia 0.6 #973
Conversation
That's not a very helpful error message... |
0484ff5
to
53c7380
Compare
Somehow I think that |
4b42487
to
112ff0e
Compare
Codecov Report
@@ Coverage Diff @@
## master #973 +/- ##
==========================================
+ Coverage 78.65% 78.69% +0.04%
==========================================
Files 33 33
Lines 4000 4008 +8
==========================================
+ Hits 3146 3154 +8
Misses 854 854
Continue to review full report at Codecov.
|
all tests pass locally now. there are still some deprecation warnings though, mostly from FixedSizeArrays.jl, which Contour.jl uses. we should consider switching to StaticArrays.jl at some point. difficulty there is that it has dropped support for 0.5. Media.jl also throws a couple warnings. i would still suggest not merging this PR until folks have actually used it. i have not visually checked the appearance of any plots yet to make sure they look okay. |
wait, nevermind, the |
the now the tests are stuck on a world age problem... |
Awesome! Thanks for finding that out. There seem to be a couple bugs in 0.5 that Gadfly/Compose relied on that were fixed in 0.6 |
the world age problem is now fixed, and all tests pass locally on julia 0.5 and 0.6! would be great if someone could give it a try. you'll need to checkout master on Loess, Hexagons, and Showoff, and checkout bja/julia06 on Compose and Gadfly. there are still a couple depwarns from the Media.jl dependency, which is for Juno. and a dozen or so depwarns remain from FixedSizeArrays.jl, which Contour.jl uses. the plan is not to ever upgrade FixedSizeArrays.jl to julia 0.6, but rather to migrate everything that depends on it to StaticArrays.jl. there are also quite a few at any rate, as soon as my Compose PR is merged and tagged, the travis tests should pass for this PR on nightly, and i think we can merge. |
Is StaticArrays a drop in replacement for FixedSizeArrays? Because then we could move over to StaticArrays for both 0.5 and 0.6. Otherwise, we might have play around with conditional dependencies or something. |
the names of types have changed, but otherwise it's drop-in. whenever someone gets around to migrating Contour from FixedSizeArrays to StaticArrays, Gadfly will either have to drop support for julia 0.5 or add an upper bound on the Contour version. until then, we just have to live with a few deprecation warnings. |
StaticArrays appears to have 0.5 as the lower bound so we could probably migrate Contour right now without dropping 0.5 support. |
Ah, I missed that. I just read the README, but I guess that was out of date. I guess the moment that 0.6 drops we can make a final release for 0.5 and then move master solely to 0.6 and switch to staticarrays. |
Does anything else need to happen before you guys can make a 0.6-compatible tag of Gadfly? |
someone should check that it works in the various IDEs... Juno, IJulia, JuliaBox. i've only tested on the REPL. specifically, Media.jl throws a few dep warns. |
IIRC the version of 0.6 on JuliaBox is pretty old so whether Gadfly works there is probably not entirely representative. If I may, I'd recommend that if it works in the REPL you'd might as well tag a version since mostly works is better than not working at all, and as Tony says, "tags are cheap." |
As @tkelman says, tagging is cheap. Lets go ahead and go forward with tagging a release so we have 0.6 compat. |
tests are still failing to a macro call in Compose:
can anyone give me a hint here?
there is still also the
show
/display
code to port.