@tburrows13 thanks for the careful review. I'm in the middle of a trip now, but gonna update this following your comment ASAP, probably during the next wekeend.

Sure, no hurry

this is ready for a new review/merge .

So, could we merge this or an extra review is needed?

@Zulko could you check and merge this one? It's blocking the other refactors proposed.

Alternatively, give me permission on the repo. (I'll use it with care, promise)

I've got no issues with merging, so I'll go ahead and do it. I'd happily support giving @mgaitan the Collaborator role as well. I think if you merge the current master branch into your other PRs, then they'll be sorted now.

excellent, thanks!

Sure! I've been away this last weekend, but now that my university term has finished, I'm keen to get v1.0.2 out within a few days. Feel free to comment on any PRs that you think would be suitable and I can add them to the milestone.

Thank you so much guys for taking care of the library! I am a bit out of touch but super happy to see that!

Martin I sent you a collaborator invitation, maybe add your name in the maintainers list in the Readme? Maybe also mark Tom and yourself as main maintainers, since you are currently the most up-to-date on the library?