[Dhairya-007]

Two problems in geojson.utils.

coords yields whole coordinate tuples, not one-element ones

It was annotated Generator[tuple[float]], but it yields each complete coordinate:

>>> list(coords(LineString([(-115.81, 37.24), (-120.5, 40.1)])))
[(-115.81, 37.24), (-120.5, 40.1)]
>>> list(coords(Point((1.0, 2.0, 3.0))))
[(1.0, 2.0, 3.0)]

So reading the latitude of a 2D coordinate was a type error:

for c in coords(line_string):
    x, y = c[0], c[1]   # error: Tuple index out of range  [misc]

Changed to tuple[float, ...], since 2D and 3D coordinates are both possible.

The map_* callables were Incomplete and partly wrong

All three took Callable[[Incomplete], float | Geometry]. That return type is wrong for map_tuples, whose implementation calls tuple(func(c)) — so the callable has to return an iterable of floats. A coordinate-swapping function was rejected:

map_tuples(lambda t: [t[1], t[0]], line_string)
# error: Argument 1 to "map_tuples" has incompatible type ...; expected "Callable[[Any], float | Geometry]"

Replaced the Incomplete callables with what the implementations actually do:

• map_coords applies func to individual coordinate values — tuple_func calls func(coord[0]) and func(coord[1]) — so Callable[[float], float]
• map_tuples applies func to a whole coordinate sequence and wraps the result in tuple(...), so Callable[[Sequence[float]], Iterable[float]]
• map_geometries passes each geometry through func

Verified against geojson 3.3.0 by introspecting the runtime behaviour, and the four errors above are gone under mypy --strict.

[github-actions]

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