Tim Hoffmann
Tim Hoffmann
When you look at REST APIs, explicit versioning of the API is common and good practice. I'd argure that our backend API is semantically quite the same.
The point is that you explicitly version the API. With EffVer (or SemVer) on the API, you have a direct insight on whether and how much the API has changed....
> I am in favor of adding a version on the backends (like we do with on the fontcache). The point is for backends to communicate to us what API...
> One question I have is in regards to whether this could be indicated somehow in the backend registration process instead? When a backend wants to register with us, they...
> I know (because I can look at matplotlib's source) what kind of capability sniffing is performed by matplotlib IMHO we should communicate our API explicitly. "Look at our source...
> > Look at our source code to understand our API" is not good enough, in particular if you want to support many versions. > > In theory that is...
> What I object to is trying to claim "this is the stable mpl backend api v1.0" when that API has never really been specced or made stable, I'm happy...
@anntzer is the new wording acceptable to you?
I think this should have at least 2 approvals. So leaving open.
In the context of ```python # [here Interactive panning and zooming is pretty responsive] # Time the canvas drawing: t_no_line = min(timeit.repeat(fig.canvas.draw, number=1, repeat=3)) # (gives about 25 ms) #...