Emmanuele Bassi

I agree about `pedantic`, so even with `warning_level=3` I'd drop it with additional compiler warnings; the other option is to add a bunch of warnings ourselves on top of `warning_level=2`.

No real plan, at the moment. The main use case is embedding a sub-project. I can spin up a release, but it's low on my to do list.

> Why not? Because that would require freezing the API, and would also require me to devote more time than I currently can spare. I'm not closing the door on...

> So in current situyation it could be no repeatable builds of other projects .. I have no idea what you mean with that. Linking against mutest as a shared...

g-ir-scanner doesn't know anything about `__float128`, but it's a system header so it shouldn't matter at all—and it definitely shouldn't segfault. A trace of the segfault would help. If you...

Would it be possible to split it into two separate commits: 1. the change for the Python installation 2. the GitHub workflow update and rebase it on the main development...

From the build log: `FileNotFoundError: [WinError 2] The system cannot find the file specified`

You should file an issue on the [GTK issue tracker](https://gitlab.gnome.org/GNOME/gtk/-/issues).

This MR removes a bunch of code, so additional testing is appreciated.

I was not planning on adding that API, but I would not say no to a pull request…