Update section __init__ type hints

[elegantiron]

Update left, bottom, width, and height to hint that they accept int or float

fixes #2525

[elegantiron]

working on the failed checks

[einarf]

We do have AsFloat that would likely be more specific in this case?

arcade/arcade/types/numbers.py

Line 14 in 7717e3f

AsFloat = Union[float, int]

[elegantiron]

Looking at the docs for type hinting:

# On Python 3.10+, use the | operator when something could be one of a few types
x: list[int | str] = [3, 5, "test", "fun"]  # Python 3.10+
# On earlier versions, use Union
x: list[Union[int, str]] = [3, 5, "test", "fun"]

We should either use Union or we should drop support for Python 3.9.

I assume dropping support for Python 3.9 is going to be significantly more involved than using Union to stay compatible and people will prefer using Union over changing the supported versions.

[einarf]

We should either use Union or we should drop support for Python 3.9.

I think from __future__ import annotations backports everything even for 3.9.

[pushfoo]

We should either use Union or we should drop support for Python 3.9.

TL;DR: Soon (in a few months)

For the moment switching back to Union would be counter-productive:

1. It's eight months until Python 3.9 EOLs in October of 2025
2. We've been incrementally switching to | in anticipation of that

As a bonus, the doc cited is mypy doc. They have ideas which clash with our codebase(s). Specifically, we face the same issues as pyglet does with mypy due to Rect being a NamedTuple (from the pyglet pyproject.toml):

[[tool.mypy.overrides]]
# mypy incorrectly reports issues everywhere in pyglet.math because:
# 1. pyglet.math is almost entirely typing.NamedTuple subclasses
# 2. The mypy project has the following long-standing stance on
#    supporting collections.namedtuple and typing.NamedTuple:
#    "Duplicate of #5613, still low priority, better use dataclasses,
#    as suggested above."
#    https://github.com/python/mypy/issues/5944#issuecomment-441285456
module = "pyglet.math"
ignore_errors = true

[pushfoo]

We do have AsFloat that would likely be more specific in this case?

I think it was lazy shorthand / a way to make pyright pass in specific cases.

[pushfoo]

In my eyes, this has better legiblity than AsFloat. The tab-completion ergonomics aren't as good, but 🤷