-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
switching _pytest.code to new style classes broke the api #2398
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
Comments
Which class is affected by this? Here's a crazy idea: What about adding a |
IIRC originally it was It is important to note that the purpose of #2179 was to exactly remove the subtle differences between old and new classes in Python 2 because pytest wasn't consistent regarding this with some classes subclassing
I agree with the "crazy" part of it. 😛 I would rather not make things worse by adding black magic just to fix this, hehehe. |
@The-Compiler its next to impossible to ensure we didn't mis some random painful edge-cases, i'd prefer admitting an accidental break so people can review and fix their stuff |
1 similar comment
@The-Compiler its next to impossible to ensure we didn't mis some random painful edge-cases, i'd prefer admitting an accidental break so people can review and fix their stuff |
@The-Compiler its next to impossible to ensure we didn't miss some random painful edge-cases, i'd prefer admitting an accidental break so people can review and fix their stuff |
As discussed in the mailing list, unfortunately this might break APIs due to the subtle differences between new and old-style classes (see pytest-dev#2398). This reverts commit d4afa15 from PR pytest-dev#2179.
Can we close this given that #2414 has been merged? |
@nicoddemus @hpk42 this one is fun
due to
we changed the behaviour of feature detection on
report.long_repr
The text was updated successfully, but these errors were encountered: