John T. Wodder II

`__requires__` is not a standard. [It originated in setuptools](https://setuptools.readthedocs.io/en/latest/pkg_resources.html?highlight=__requires__#workingset-objects), and then one of the setuptools developers combined the idea with support for pip to create pip-run.

I don't know of any precedent; I just feel that a class being generic should be indicated on the class name itself and not only as part of the base...

Manually adding type annotations is time-consuming and mind-numbing. Instead, I'm going to refer to , which lists several tools for automatically adding type annotations to Python source, along with ,...

I am also seeing a similar problem. If I have this code: ```python from __future__ import annotations from pydantic import BaseModel from typing import Optional class Foo(BaseModel): foo: Optional[str] =...

Fine, I'll take a commit-bit.

Question: How will releasing to crates.io be handled going forwards?

@yarikoptic Warnings are just supposed to be subclasses of [`Warning`](https://docs.python.org/3/library/exceptions.html#Warning); I doubt that trying to mix in a regular exception would work.

* The project does support setuptools 30.3.0; it's just that asv installs setuptools 30.3.0 exactly and also doesn't isolate builds, which causes a problem with a dependency that requires a...

> If you have a hard dependency on something which needs setuptools higher than 30.3.0 then your code also only supports higher than 30.3.0. Setuptools is a build dependency for...

Here are the logs from a run of `asv run --show-stderr --verbose HEAD^1..HEAD` with `setuptools >= 30.3.0` in our project's `pyproject.toml`: https://gist.github.com/jwodder/0e5bb56107d24d783aff9d7980dcde1a > `python -m build && python -mpip wheel...