Plots 2.0

[BeastyBlacksmith]

This is the development branch for Plots 2.0.

What changed

• No default backend in PlotsBase, Plots becomes a wrapper for PlotsBase + GR (per [RFC] Plots 2.0 #4565 (comment)), making it non-breaking;
• Backends are purely extensions with no @require;
• The internals are more organized into modules and moved around;
• Backend init and backend code is only found in its extensions, this should help with backend interference and annoyances about initialization and precompilation of plots. This should make backends modular and implemented much easier and without hacks into Plots.jl codebase;
• Restored Preferences chosen backend;
• ...

Example:

import UnicodePlots
using Plots 
unicodeplots()
plot(1:10)

What works

• PlotsBase and Plots tests;
• Preferences based backend selection.

What does not work

• Precompilation statements for Plots when using an alternate backend: cannot @eval Main import UnicodePlots => most of the precompile statements are cached in PlotsBase now.

Help needed:

• write backend agnostic precompile statements for PlotsBase
• backport changes from v1 since last rebase
• report breakages
• move documentation back into this repo
• start updating the docs
• update the news.md

Decisions to be made

• deprecate inspectDR ?
• move to column major order ?
• change the defaults

Issues needing attention please add more or checkoff resolved:
#4565 (comment)
Copy of that:
Labeled issues:

• [FR] change minorticks semantics #4532
• [FR] auto ylim calculation #4028
• [FR] Safe figure saving #3001
• [BUG] Cycling arguments #2980
• support scalars for hline! and vline! #2129
• Should layout be column major? #2047
• [FR] PythonPlot/PythonCall alternative to PyPlot/PyCall #4181
• [FR] Use Preferences.jl to configure default loaded backend #4513
• [FR] remove explicit GR dependency from Project.toml #4631
• [BUG] Inconsistency With Measurement Units In API #4350
• [FR] redesign backend dependencies #4567
• [FR] Harmonize how series data are used #4596

Labeled PRs:

• cleanup: drop deprecated pgfplots #4326
• GR margin 0-point set to allow no padding #3942
• Reduce number of exported names #3744
• Rework adding legends #3732
• WIP: Fonts #3473
• Remove StatsPlots warnings #3357
• Move @df macro to Plots #3351
• Rework adding legends Rework adding legends #3732

---

Closes #4326

[BeastyBlacksmith]

@t-bltg do you intend to release this as a 1.x release?

[t-bltg]

If we can make it non breaking, it would make things easier and end endless discussions.

[BeastyBlacksmith]

Well, there would be a few changes that we'd need to roll back for this, like removal of pgfplots and I removed some functions also.

But I also don't quite see how to make switching of backends non-beraking since, what was

using Plots
pythonplot()

is now

using Plots
import PythonPlot
pythonplot()

[isentropic]

I still don't get why can't 2.0 be breaking and why having a helpful error message isn't enough as a solution as per my comment in the issue #4565. Having GR as the default backend feels bad to me. I understand that nobody changes the backend but this way backend malfunctioning could be diagnosed easier.

Then if the backend doesn't work people can learn about other backends. I really don't buy the keep gr argument by searching GitHub code. Plots 2.0 isn't just for the users but also for debugging and long term stability.

Keeping gr as the default is not good imo. Flux got rid of it's CUDA for this reason and it works fine, new users can adapt we just need to leave good info/warn messages

[isentropic]

I'm sorry that I'm late into the discussion and if some undoing needs to be done but we should prioritise long term good with 2.0. GR being the default is also what defers people from using plots, if users can learn about the flexibility that's great too. Pyplot imo works more stably with various fonts and scalings.

The purpose of package extensions is exactly this. Splitting into plotsbase and just plots to keep the standard interface means that we never need to go to 2.0 then.

2.0 by definition is breaking and that's ok. Plots is not a low level package and hardly any packages take dep on Plots. Interactive usage is easier to adapt to 2.0 anyways in case the help messages are well stated.

We also need to think about column major order to make Plots play nicely with others and streamline the column major way. These two changes are by far the most important, both being breaking and that's ok cause it's 2.0.

[isentropic]

I get why people might object with needing to import GR explicitly, but you know adding such import help long term in that people would realize that there are more backends than just GR, and that the errors are coming because of 'import GR' not 'using Plots'. Im not kidding half of our issues are because GR didn't build or something like that. In the current scenario users try to import Plots it errors and then there's frustration. With gr free plots GR will throw it's warnings right awa and we can throw warnings and stuff like your GR loading failed, try these other backends.

[t-bltg]

But I also don't quite see how to make switching of backends non-beraking since, what was

I've omitted this, so I've restored the 2.0 label.

We also need to think about column major order to make Plots play nicely with others and streamline the column major way.

I get this, but if no one implements it, this shouldn't block a release.

Having GR as the default backend feels bad to me.

I would be in favor of dropping GR as the default backend. But on the other end, adding PlotsBase without any backend dependency seems a good compromise.

In #4914, I've finalized the way modules and extensions should be written with a lot of cleanups, and restoration of the precompile statements, but unfortunately, it broke the reference tests in subtle ways. What a mess !

I like the new splitting of PlotsBase into smaller modules initiated in this branch, but it needs more work and cleanup, without breaking the tests.

[t-bltg]

I've made progress and fixed the tests in #4914, everything is passing locally, and partially in CI.

Currently, there is no solution to generate precompile statements for a different backend than GR in Plots since we cannot @eval Main import UnicodePlots for example.

So we need at least to generate backend independent precompile statement for PlotsBase.
==> EDIT: done in #4914.

[t-bltg]

@BeastyBlacksmith, how can we move forward now ?

Embedded modules need more cleanup, but at least the port to extensions is now complete, with 100% previous tests passing.

[t-bltg]

GraphRecipes and StatsPlots are now integrated into Plots repo, so no more commits should be merged in https://github.com/JuliaPlots/GraphRecipes.jl or https://github.com/JuliaPlots/StatsPlots.jl.

[t-bltg]

@BeastyBlacksmith, can you fix the DOCUMENTER_KEY issue so that we can have dev docs for v2 deployed ?