cortadocodes

@DanielBok I've made a pull request [here](https://github.com/DanielBok/nlopt-python/pull/34) - would you be able to allow the `build` workflow to run to test if it builds ok for M1?

Unfortunately I haven't heard from the maintainer so I can't make any more progress on this

Thanks @DanielBok and congratulations!

The MacOS desktop app is doing similar things. My default browser is avoided and links open in what looks like Safari without the toolbar. Please open links in the default...

Links seem to be opening in my default browser now even though there hasn't been an update released

The error I'm getting at build time is: ``` > [16/16] RUN ./gradlew assembleFdroidBeta -Parm64 && ./gradlew clean: 0.183 Downloading https://services.gradle.org/distributions/gradle-8.6-bin.zip 4.356 ............10%.............20%............30%.............40%.............50%............60%.............70%.............80%............90%.............100% 379.1 379.1 Welcome to Gradle 8.6! 379.1...

Originally it was an open offer as you could use docker for multiple things here, then it was going to be to facilitate reproducable builds. Realistically I think I've taken...

It was to build a reproducible build for android. I looked at Signal's approach for inspiration so we should give them credit if their approach is followed: https://github.com/signalapp/Signal-Android/blob/main/reproducible-builds/Dockerfile

Implemented here: https://github.com/django-guardian/django-guardian/pull/835

Personally I find `asserts_errors` a useful way to reduce boilerplate in my tests. I don't think it should be removed but agree with @thclark that `assert_no_errors` would be a better...