-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
gh-123596: Fixed return None when getattr the sys.tracebacklimit. #125777
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
Conversation
rruuaanng
commented
Oct 21, 2024
•
edited by bedevere-app
bot
Loading
edited by bedevere-app
bot
- Issue: Python implementation of traceback limit does not default to 1000 as documented in 3.13 #123596
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add tests for this change.
Please let me finish the work at hand. I'm about to add everything :) |
Please don't create a pull request until it's ready according to you. Otherwise people might want to review it without knowing that it's incomplete. |
I see. Maybe I should respond to your request quickly. So I created a draft pull. I hope no one will misunderstand. I'm working this. |
I'm not sure it's worth adding the test. It seems like already exists. And his handling of tracebacklimit is really only 1000 when it's undefined. cpython/Lib/test/test_traceback.py Lines 3006 to 3015 in 7d88140
Edit: |
And this change passes the existing test for test code:
changed diff:
changed output:
When I remove
For the above test code
|
I actually feel like this change could probably be merged with the PR that adds |
I have added a test that checks if the call stack is 1000. Can it skip NEWS? It seems that this change is implicit. |
I'll close this PR and hand the change over to the original author for fix. |