A5rocks

I'm going to leave this open *but* disable the integration for now.

Fedora and freebsd testing (and maybe another platform), both of which GitHub actions can do but only by literally just using qemu :(

FYI don't forget that we also have an open PR for hatchling. If a little out of date... And `pip-tools` supports (standards-compliant) `pyproject.toml`.

For what it's worth, I've when thinking about builds.sr.ht replacements and seen how e.g. snmalloc uses qemu to run freebsd stuff in github actions: https://github.com/microsoft/snmalloc/blob/6b8f3338c71fb06a3609ef935a8579b7bda7e07e/.github/workflows/main.yml#L117

To try to illustrate the difference between a management tool and a build backend, let me focus on a specific kind of "management tool": build frontends. Here's a few build...

I think getting rid of `setup.py` is in itself a worthwhile goal! But I agree with the python version thing -- that's my main problem with `pip-compile` specifically ATM. I...

I don't think it's anything specific against hatchling, moreso that the other pr which was just closed was in limbo. But we're still considering hatchling, I think? Main point against...

I forgot about updating this issue regarding the `strict_exceptiongroups=True` default change in v0.25.0. [See release notes for more information.](https://trio.readthedocs.io/en/stable/history.html#breaking-changes) You can switch it back either globally (with `trio.run`'s parameter) or...

Just popping by to mention that #2790 probably will end up not making a change to how we have requirements files (at least if I have my way and there...

I don't think using a manual stage would make sense, because either way we'd have to commit and push the changes which are the main issues with the current workflow.