[issue36026] Different error message when sys.settrace is used (regressions)

Change by SylvainDe : -- type: -> behavior versions: +Python 3.7, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue36026] Different error message when sys.settrace is used (regressions)

Serhiy Storchaka added the comment: Looks this is due to the method calls optimization (issue26110). We now avoid to create a temporary bound method, and an error with different message is raised on this path. >>> set.add(0) Traceback (most recent call last): File "", line 1, in

[issue36026] Different error message when sys.settrace is used (regressions)

SylvainDe added the comment: This is mostly true and I agree that error messages are not part of the API. However, I'd like to add the following points: - the error message was more meaningful before - the fact that having system.settrace used or not changes the behaviour makes me think

[issue36026] Different error message when sys.settrace is used (regressions)

Steven D'Aprano added the comment: Do I correctly understand the reported problem here? set.add(0) correctly raises TypeError in each case, but: (1) the exception message changes between versions; (2) and also changes depending on whether or not sys.trace is active. I don't think the

[issue36026] Different error message when sys.settrace is used (regressions)

Change by Karthikeyan Singaravelan : -- nosy: +serhiy.storchaka, vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue36026] Different error message when sys.settrace is used (regressions)

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36026] Different error message when sys.settrace is used (regressions)

New submission from SylvainDe : Context: Follow-up from https://bugs.python.org/issue35965 which was closed when we assumed the issue was on the coverage side. After nedbat investigation, it seems like the issue comes from call to "sys.settrace". Issue: -- A test relying on