First check

• I added a very descriptive title to this issue.
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the FastAPI documentation, with the integrated search.
• I already searched in Google "How to X in FastAPI" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answ

Long story short

I've been using low-level machinery exposed by aiohttp for my framework.
When I learned about handle_signals=True I started testing it and it turned out that my process always exited with return code 1 on SIGTERM and SIGINT.

This was confusing and I thought that it's a bug. But then, after diving into the code deeper, I realized that with this option enabled, aioht

Our environment variable documentation should include some justification or context for each case, by doing one of the following for each envvar:

• Make it clear that an environment variable is specific to HTTPX. (Probably only relevant to anything prefixed by HTTPX_)
• Make it clear that an environment variable is used as a convention by

Great stuff! I'd love to use this in magic-wormhole.. I only need the DataChannel, though. Any idea how hard it'd be to define a 'feature' for the codecs, so pip install aiortc[video] gets you the dependencies on the codecs, but pip install aiortc[datachannel] does not?

Example of usage:

users = await User.filter(first_name__ilike="c%r")

I know this can be done with startswith and endswith, but there are cases where using the LIKE operator is better:

users = await User.filter(first_name__ilike="j_r%")

This would be used to match Jeremy, Jorge, Jordan...