You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# pyright .
test_test.py
test_test.py:10:12 - error: Operator "+" not supported for types "Unknown | object" and "Unknown | object"
Operator "+" not supported for types "object" and "object" (reportOperatorIssue)
test_test.py:10:32 - error: Argument of type"Literal['2.0']" cannot be assigned to parameter "func" of type"_TFunc@__call__"infunction"__call__"
Type "Literal['2.0']" is not assignable to type"(...) -> Any"
Type "Literal['2.0']" is not assignable to type"(...) -> Any" (reportArgumentType)
test_test.py:10:61 - error: Argument of type"Literal['2.5']" cannot be assigned to parameter "func" of type"_TFunc@__call__"infunction"__call__"
Type "Literal['2.5']" is not assignable to type"(...) -> Any"
Type "Literal['2.5']" is not assignable to type"(...) -> Any" (reportArgumentType)
3 errors, 0 warnings, 0 informations
If I delete @allure.step decorator, everything starts working fine.
What is the expected behavior?
Expected behaviour is taht type checking by pyright would pass here
What is the motivation / use case for changing the behavior?
I'm submitting a ...
What is the current behavior?
Pyright(1.1.380) validation fails for functions calls if they have an allure step decorator.
If the current behaviour is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Here is a abstract code example that shows an issue
Which leads to a following output:
If I delete
@allure.step
decorator, everything starts working fine.What is the expected behavior?
Expected behaviour is taht type checking by
pyright
would pass hereWhat is the motivation / use case for changing the behavior?
Please tell us about your environment:
Python 3.12.3
pyright: 1.1.380
Other information
The text was updated successfully, but these errors were encountered: