Trying to understand the implementation of the API wrapper, and I'm wondering how the version of the graphBLAS API is handled? It looks like the API moves slowly, but it does move ( eghttps://graphblas.org/ saysv1.3.0 on September 25, 2019 andv2.0.0 on November 15, 2021 ).

I ask because it looks like the mappings are relatively manual - a lot of hardcoded names, etc. - rather than something where you're programmatically generating bindings directly from the API. Having just started taking a look at the implementation I am assuming there's a good reason for that, so completely fine, but is there some place where you specify that "this version of python-graphblas is compatible with x version of graphblas API?"

I see that a version ofsuitesparse-graphblas is pinned, so presumably that also pins some specific version of the API?

In any case, seems like something that would be worth having in the docs if not implemented in the code - there's a statement on python version here:https://python-graphblas.readthedocs.io/en/stable/getting_started/faq.html#what-is-the-version-support-policy but I don't find one for graphBLAS API version

edit: part ofpyOpenSci/software-submission#81