According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉

Passing:

• python tests/runtests.py --run-stubtest stubs/geojson
• ty check on the geojson source and tests, using these stubs via --extra-search-path

I know that the stubs are still marked as draft, but I've had a brief look. One thing I noticed is the use of Any: In most cases, there needs to be (brief) comment of why Any was used or what types are accepted. It should also be clear, why Any has to be used instead of a "real" type. One notable exceptions where we don't require an explanation is dict[str, Any].

If you need a placeholder for "not fully typed yet", either leave out the annotation or use Incomplete (imported from _typeshed) when that's not syntactically impossible. For example, you could use Iterable[Incomplete] to mark that you know that it's an iterable, but the exact types in the iterable are to be determined. On the other, something like this is useful, if using concrete types is not possible or desirable:

def foo(x: str) -> Any: ...  # returns str if x starts with "bar:", int otherwise

@srittau Thanks for the quick feedback! I'll take another pass at it.

Do you have any advice for typing the coordinates parameter in the geojson.geometry module? Something like None | Feature | tuple[float, float] | Iterable[tuple[float, float]] | Iterable[Iterable[tuple[float, float]]] etc. seems too crazy and still doesn't catch deeply nested edge cases.

Or should we overload the __init__ signatures for each Geometry child class?

I haven't looked at the type, but you could try a recursive type alias. Alternatively use Any at some depth (probably not directly as argument as that would allow completely incorrect values), and add a comment.