no special cases for float and complex¶

python's typing spec special-cases float to mean int | float and complex to mean int | float | complex. basedpython does not. in a .by file, float is just float and complex is just complex

def takes(x: float) -> None: ...

takes(1.0)
takes(1)   # rejected: `float` does not include `int`

scope¶

the rewrite fires only in type-expression positions:

• variable annotations
• function parameter and return annotations
• type alias right-hand sides
• typevar bound and default expressions
• recursive into generic subscripts (list[float], dict[str, float])
• recursive into the first argument of Annotated[…]

bitwise-or unions (float | None), bitwise-and intersections (float & A) and Literal[…] are handled correctly; literal-value positions inside Literal[…] are not type expressions and are left alone

value-position uses of float / complex (calls like float(x), isinstance(y, float)) are left alone — they refer to the class object, not to the type

interop with .py¶

a .py file imported into a .by file keeps python's typing-spec meaning of float / complex. the strict basedpython meaning only applies inside .by files; consumers reading the transpiled .py output see the strict types too