-
Notifications
You must be signed in to change notification settings - Fork 16
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
Deprecated assertEquals (and similar methods) don't work in marbles #85
Comments
I ran this in pdb and found the following:
It seems that we're incorrectly assuming the last argument here is the msg and packaging that up, rather than forwarding it along. |
This is because we inspect the method signature to find the Not sure exactly what to do here, perhaps we should detect when the assertion method is one of these passthroughs |
…ters This deals with the "deprecated assertion names" like assertEquals forwarding to assertEqual, and possibly others like them. Closes #85
…ters This deals with the "deprecated assertion names" like assertEquals forwarding to assertEqual, and possibly others like them. Closes #85
…ters This deals with the "deprecated assertion names" like assertEquals forwarding to assertEqual, and possibly others like them. Closes #85
Note : In Python 3.11 the deprecated aliases have been removed in python/cpython#28268 |
Description
Tried to run a
unittest
test that uses the deprecated nameassertEquals
instead ofassertEqual
.What I Did
The
assertEquals
tests fail with the following stack:Expected behavior
I expected
assertEqual
andassertEquals
to behave the same. Instead,assertEqual
does the expected thing, whileassertEquals
fails with aTypeError
The text was updated successfully, but these errors were encountered: