I expect GraphBLAS to become much more visible in the broader Python scene in the coming year or two. In the spirit of being Pythonic, there should preferably one (and only one) library for writing GraphBLAS code in Python. Readability counts.

@eriknw, I feel like you have been drifting ever closer to wanting an immediate execution mode and things like A += expr to work. While there are things about pygraphblas that you don't like, it seems like some decisions on these fronts are growing on you.

I think we are within striking distance of closing the gap between grblas and pygraphblas. And while we started from a position of "purity", practicality now feels more urgent. Hence, I am willing to bend a little if we can get unity and and single community going forward, rather than a fragmented ecosystem.

I still like our use of delayed A.T, A.S, etc and the A(accum=..., mask=...) << expr syntax. I think that is actually quite elegant and readable. But the more we can move to an immediate-execution model, the less surprising things will be for new users.

Let's set aside time in our weekly meetings to brainstorm what this unification could look like, as well as the barriers needed to overcome.