-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
gh-130197: Remove obsolete pygettext tests #130198
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
StanFromIreland
commented
Feb 16, 2025
•
edited by bedevere-app
bot
Loading
edited by bedevere-app
bot
- Issue: pygettext: Improve test coverage #130197
Requesting @tomasr8 |
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.
I don't think we need to remove those tests. They are testing that --docstring
works from end-to-end. So I think we can keep them.
This comment was marked as resolved.
This comment was marked as resolved.
@tomasr8 what was the plan for the future of it? Deprecate the option? |
Considering the issue discussion, let's remove the tests while trying to have an E2E test for --docstring
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.
I'm no expert in pygettext
, so I'll let @tomasr8 and @serhiy-storchaka decide. However, Serhiy wanted to keep all tests I think (see #130197 (comment)) so I think we can also close this PR but keep the issue to improve the test coverage instead (unless there's another issue for that)
Yes let's close this. I think Serhiy is right in the sense that even though the tests are currently not doing anything, if we ever change the implementation (though unlikely), they will be useful again to prevent potential regressions. Sorry @StanFromIreland for the extra work :/ I'll update the issue so we can reuse it for improving the test coverage, I think it's better than opening a new one. |