-
Notifications
You must be signed in to change notification settings - Fork 475
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
Update multiple ImageCore compat from 0.7 to 0.8 #392
Update multiple ImageCore compat from 0.7 to 0.8 #392
Conversation
Things worth noting..
|
This is probably the right way to do it. In retrospect I was being silly by not just nuking the upper bounds as soon as the bottlenecks started becoming apparent. Looks like this will need a rebase. |
Ok. I've rebased. Apologies, I shouldn't have brought the ImageMorphology changes in here without closing the other PR |
Thanks for doing this! |
Can you rebase on the master branch @ianshmean? |
Hi @ianshmean , I just noticed this thread now (I'm a maintainer of Caesar.jl) -- is this issue still a problem? I'm a little worried if you are indeed seeing the
A new version of Caesar (v0.3.1) was tagged yesterday but it's compat only goes up to (testimagecorecaesar) pkg> status
Status `~/.julia/environments/testimagecorecaesar/Project.toml`
[62eebf14] Caesar v0.3.0
[a09fc81d] ImageCore v0.8.2 ASIDE: Caesar.jl master now has compat at |
@timholy Hopefully this reduces the pain.. Replaces and expands #389
All add-able to a blank slate package environment, except
Caesar.jl
due to JuliaLang/Pkg.jl#1169Passing local tests on MacOS 10.14.4 (except for
Caesar.jl
which is untested due to above)Should we leave
Caesar
unchanged, given not tested?