Closed Masacroso closed 3 years ago
Thanks @Masacroso sorry we couldn't figure out what is going on. I verify that I don't see AbstractPlotting in the dependencies here.
Hopefully you found a workable solution
Thanks @Masacroso sorry we couldn't figure out what is going on. I verify that I don't see AbstractPlotting in the dependencies here.
Hopefully you found a workable solution
Hi Spencer. What Im doing is using two different environments, as easy as call using Pkg; Pkg.active("myOtherEnv")
when needed. After some investigation I see that AbstractPlotting.jl
is installed when its installed WebIO.jl
, however it is not a direct dependency so it must be a dependency of some of it dependencies, or some incompatibility with newer versions of GLMakie.jl
that uses the library Makie.jl
instead of AbstractPlotting.jl
.
Anyway is not due to your package, and unfortunately I dont found what package have at dependencie AbstractPlotting.jl
to try to find a global solution. Anyway I hope it will be fixed with time.
This is not to describe a bug, it is to suggest an improvement on the library PlotlyJS to make it compatible with the Makie plot system. What I mean is that, by now (in PlotlyJS version 0.18.3) one of it dependencies is AbstractPlotting.jl, what is a deprecated library used by the Makie system.
Then if I have both GLMakie and PlotlyJS installed then the Makie library doesn't work, at least in some plots, in the REPL, Jupyter notebooks or in VScode. So, I think it would be easy to change the dependency on AbstractPlotting.jl to dependency in Makie.jl, what is now the actual library that have the functions that previously where in AbstractPlotting.
UPDATE: reading the toml of PlotlyJS this dependency doesn't appear, however it is installed every time I install PlotlyJS, and uninstalled every time I uninstall it.
UPDATE 2: the behavior seems unrelated directly to PlotlyJS, maybe it is related to some of it dependencies. Maybe we can close this issue.