You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The goal is to replace d by plotattributes inside @recipes. See here for the original issue. Of course that is a change that breaks a lot of packages, so there was a plan how to coordinate things. I started implementing it, but @mkborregaard wanted to wait until julia version requirement is bumped to 0.7. However I probably won't have time for this when we upgrade to 0.7. So I propose here a better plan, where almost all work can be done now, without breaking anything.
Step 1
Allow usage of both d and plotattributes inside @recipes. Without any deprecation warning.
Tag a new release for RecipesBase.
I searched all packages that depend on Plots or RecipesBase and none of them used the word plotattributes inside a recipe. So this is a safe step.
Step 2
Update d to plotattributes inside Plots.
Tag a new release for Plots.
Doing this after tagging Step 1 is important so all tests can pass.
After this step it is safe to use plotattributes instead of d in any other package.
Step 3
PRs to all packages that depend on Plots or Recipes to replace d by plotattributes.
While a lot of packages depend on these, only a few are using d:
DynamicMovementPrimitives
ImplicitEquations
LPVSpectral
PlotRecipes
StatPlots
SymPy
TimeSeries
ValueHistories
Step 4
When upgrading to julia 0.7 add depwarning for usage of d.
Step 5
When upgrading to 1.0 remove d altogether.
Do the maintainers of Plots agree with this?
The text was updated successfully, but these errors were encountered:
Replace d by plotattributes
The goal is to replace
d
byplotattributes
inside@recipes
. See here for the original issue. Of course that is a change that breaks a lot of packages, so there was a plan how to coordinate things. I started implementing it, but @mkborregaard wanted to wait until julia version requirement is bumped to 0.7. However I probably won't have time for this when we upgrade to 0.7. So I propose here a better plan, where almost all work can be done now, without breaking anything.Step 1
d
andplotattributes
inside@recipes
. Without any deprecation warning.I searched all packages that depend on
Plots
orRecipesBase
and none of them used the wordplotattributes
inside a recipe. So this is a safe step.Step 2
d
toplotattributes
insidePlots
.Plots
.Doing this after tagging Step 1 is important so all tests can pass.
After this step it is safe to use
plotattributes
instead ofd
in any other package.Step 3
PRs to all packages that depend on
Plots
orRecipes
to replaced
byplotattributes
.While a lot of packages depend on these, only a few are using
d
:Step 4
d
.Step 5
d
altogether.Do the maintainers of
Plots
agree with this?The text was updated successfully, but these errors were encountered: