diff options
| author | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2021-10-19 22:07:13 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-10-19 22:07:13 (GMT) |
| commit | c15ba304f35362470e29ea5626fed28366bc9571 (patch) | |
| tree | 472cb2821774b2b4c4d2453211423c8cca6c1532 /Python/ast_unparse.c | |
| parent | 5c9cab595e56aeb118bff77ece784dbac30b4338 (diff) | |
| download | cpython-c15ba304f35362470e29ea5626fed28366bc9571.zip cpython-c15ba304f35362470e29ea5626fed28366bc9571.tar.gz cpython-c15ba304f35362470e29ea5626fed28366bc9571.tar.bz2 | |
bpo-39679: Add tests for classmethod/staticmethod singledispatchmethods (GH-29034) (GH-29072)
In Python 3.8 and 3.9, stacking `@functools.singledispatchmethod` on top of
`@classmethod` or `@staticmethod` caused an exception to be raised if the
method was registered using type-annotations rather than
`@method.register(int)`. This was not caught by unit tests, however, as the
tests only tested the `@method.register(int)` way of registering additional
implementations. The bug is no longer present in Python 3.10+, but
`test_functools.py` is still lacking regression tests for these cases. This
commit adds these test cases.
(cherry picked from commit ad6d162e518963711d24c80f1b7d6079bd437584)
Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>
Diffstat (limited to 'Python/ast_unparse.c')
0 files changed, 0 insertions, 0 deletions