-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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.
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
Add regression tests for builtins.pow
and object.__reduce__
#7663
Changes from 7 commits
49a0cea
527a48c
6adc928
678b5af
62209c3
8d3db2c
632a75f
78b9dd0
9d3650f
b2e59b5
0e2165f
62a3916
1859f73
1ae215b
c4d493a
8051080
5aa49a2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
## Regression tests for typeshed | ||
|
||
This directory contains regression tests for the stubs found elsewhere in the | ||
typeshed repo. Each file contains a number of test cases, all of which should | ||
pass a type checker without error. | ||
Comment on lines
+3
to
+5
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In the long term we should probably also allow test that fail a type checker to be able to test the negative case. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yup. Once we're running mypy on this directory, we can do that by |
||
|
||
The internal structure of this directory should mimic typeshed as a whole. | ||
However, unlike the rest of typeshed, this directory largely contains `.py` | ||
files. This is because the purpose of this folder is to test the implications | ||
of typeshed changes for end users. For example, the stub for `builtins.pow` is | ||
found in `stdlib/builtins.pyi`, and the regression tests for `pow` are found in | ||
`test_cases/stdlib/test_builtins.py`. | ||
|
||
100% test coverage for typeshed is neither necessary nor desirable, as it would | ||
lead to unnecessary code duplication. Moreover, typeshed has multiple other | ||
mechanisms for spotting errors in the stubs. As such, this directory should | ||
only contain tests for functions and classes which are known to have caused | ||
problems in the past, where the stubs are difficult to get right. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. While this is correct, it might need a tl;dr in bold. As discussed, it's difficult to convince some people that they don't need to write tests. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How's it look after b2e59b5? |
||
|
||
Note that, unlike elsewhere in typeshed, the test cases in this directory | ||
cannot always use modern syntax for type hints. For example, PEP 604 syntax | ||
(unions with a pipe `|` operator) is new in Python 3.10. While this syntax can | ||
be used on older Python versions in a `.pyi` file, code using this syntax will | ||
fail at runtime on Python <=3.9. Since the test cases all use `.py` extensions, | ||
and since the tests need to pass on all Python versions >=3.6, PEP 604 syntax | ||
cannot be used in a test case. Use `typing.Union` and `typing.Optional` | ||
instead. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
from decimal import Decimal | ||
AlexWaygood marked this conversation as resolved.
Show resolved
Hide resolved
|
||
from fractions import Fraction | ||
from typing import Any, NoReturn, Tuple, Union | ||
from typing_extensions import Literal, assert_type | ||
|
||
|
||
# | ||
# REGRESSION TESTS FOR OBJECT.__REDUCE__ | ||
# | ||
# The following should pass without error (see #6661): | ||
class Diagnostic: | ||
def __reduce__(self) -> Union[str, Tuple[Any, ...]]: | ||
res = super().__reduce__() | ||
if isinstance(res, tuple) and len(res) >= 3: | ||
res[2]["_info"] = 42 | ||
|
||
return res | ||
|
||
|
||
# | ||
# REGRESSION TESTS FOR POW() | ||
# | ||
assert_type(pow(1, 0), Literal[1]) # See #7163 | ||
assert_type(pow(1, 0, None), Literal[1]) # See #7163 | ||
assert_type(pow(2, 4, 0), NoReturn) | ||
assert_type(pow(2, 4), int) | ||
assert_type(pow(5, -7), float) | ||
assert_type(pow(2, 4, 5), int) # pow(<smallint>, <smallint>, <smallint>) | ||
assert_type(pow(2, 35, 3), int) # pow(<smallint>, <bigint>, <smallint>) | ||
assert_type(pow(4.6, 8), float) | ||
assert_type(pow(5.1, 4, None), float) | ||
assert_type(pow(complex(6), 6.2), complex) | ||
assert_type(pow(complex(9), 7.3, None), complex) | ||
assert_type(pow(Fraction(), 4, None), Fraction) | ||
assert_type(pow(Fraction(3, 7), complex(1, 8)), complex) | ||
assert_type(pow(complex(4, -8), Fraction(2, 3)), complex) | ||
assert_type(pow(Decimal("1.0"), Decimal("1.6")), Decimal) | ||
assert_type(pow(Decimal("1.0"), Decimal("1.0"), Decimal("1.0")), Decimal) | ||
assert_type(pow(Decimal("4.6"), 7, None), Decimal) | ||
assert_type((4).__pow__(7, 4), int) | ||
assert_type((4).__pow__(6, None), int) | ||
assert_type(complex(9).__pow__(3.1, None), complex) | ||
assert_type(Decimal("2.6").__pow__(5, None), Decimal) | ||
|
||
# These would ideally be more precise, but `Any` is acceptable | ||
# They have to be `Any` due to the fact that type-checkers can't distinguish between positive and negative numbers for the second argument to `pow()` | ||
# | ||
# int for positive 2nd-arg, float otherwise | ||
assert_type(pow(4, 65), Any) | ||
assert_type(pow(3, 57, None), Any) | ||
# float for positive 2nd-arg, complex otherwise | ||
assert_type(pow(4.7, 7.4), Any) | ||
AlexWaygood marked this conversation as resolved.
Show resolved
Hide resolved
|
||
assert_type(pow(4.7, 9.2, None), Any) | ||
assert_type((6.2).__pow__(5.2, None), Any) | ||
# See #7046 -- float for a positive 1st arg, complex otherwise | ||
assert_type((-2) ** 0.5, Any) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
assert_type()
yet? If it does, we could instead pointmypy_primer
at typeshed'stest_cases
. That way we would know if a PR to mypy breaks the tests.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
¯\_(ツ)_/¯
. Happy to have it in only one if that's better.assert_type
yet. The PR was recently merged, and might make it into 0.950, but also might not. See Release 0.950 planning mypy#12579 (comment)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mypy supports assert_type() on master (I added it last week). I am hoping to convince Jukka to put it in the upcoming 0.950 release. We should make mypy run on this directory too as soon as 0.950 is released, or use master if we're feeling brave.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update:
assert_type
has been cherry-picked onto the 0.950 branch, so we should be able to point mypy_primer at this directory as soon as 0.950 is released.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hopefully we can just run mypy regularly, no need to use mypy-primer.