-
Notifications
You must be signed in to change notification settings - Fork 348
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
Problem with setUpClass #280
Comments
Also a problem with tests from django-autocomplete-light: https://travis-ci.org/yourlabs/django-autocomplete-light/jobs/83851177 |
Seems easy to reproduce, will try to push a fix and 2.9.1 release soon! |
pelme
added a commit
to pelme/pytest-django
that referenced
this issue
Oct 6, 2015
The previous fix did not properly check the full MRO chain when looking for the super method, which then failed when used with mixins that does not define setUpClass/tearDownClass. This commit fixes issue pytest-dev#280.
Closed
pelme
added a commit
that referenced
this issue
Oct 6, 2015
The previous fix did not properly check the full MRO chain when looking for the super method, which then failed when used with mixins that does not define setUpClass/tearDownClass. This commit fixes issue #280.
This is now fixed in master, and released in 2.9.1 on PyPI! |
tomviner
pushed a commit
to tomviner/pytest-django
that referenced
this issue
Jun 22, 2016
The previous fix did not properly check the full MRO chain when looking for the super method, which then failed when used with mixins that does not define setUpClass/tearDownClass. This commit fixes issue pytest-dev#280.
mfa
pushed a commit
to aexeagmbh/pytest-django
that referenced
this issue
May 17, 2017
The previous fix did not properly check the full MRO chain when looking for the super method, which then failed when used with mixins that does not define setUpClass/tearDownClass. This commit fixes issue pytest-dev#280.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My test code is:
Raised with error
The text was updated successfully, but these errors were encountered: