Silly suggestion, but how uncomfortable would it be to just add the pyi files to the repo? They could be regenerated when someone fiddles with the bindings (maybe with quick diff on the CI to check that they're up to date?).

Silly suggestion, but how uncomfortable would it be to just add the pyi files to the repo? They could be regenerated when someone fiddles with the bindings (maybe with quick diff on the CI to check that they're up to date?).

I agree, that would probably be better. I think the content of the pyi file may depend on options selected during build, e.g. using shipped isl or not.

I think the content of the pyi file may depend on options selected during build, e.g. using shipped isl or not.

Ah, yeah, good point :\ That doesn't sound like it would work then..

Closing, done in #171.

Whoops, sorry. I totally missed this PR in the rush to get things working again...