New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

(🐞) inconsistent behavior of initial assignment (int/float in tuple) #1029

Open

KotlinIsland opened this issue Oct 26, 2023 · 1 comment

KotlinIsland commented Oct 26, 2023 •

edited

from testFloatOps.test_tuples

def f() -> None:
    a = 1
    b: tuple[float] = (a,)
    assert b == (1.0,)
    
    b = (a,)
    assert b == (1.0,)  # TypeError: int object expected; got float

Please forgive my ignorance if this has been raised already, I'm not at all familiar with mypyc.

Author

KotlinIsland commented Oct 27, 2023

Found another one:

def f() -> None:
    z: float = True
    assert z == True
    z = True
    assert z == True  # TypeError: bool object expected; got float
f()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment