-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
gh-130197: Test pygettext
output option
#133041
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
Apr 27, 2025
•
edited by bedevere-app
bot
Loading
edited by bedevere-app
bot
- Issue: pygettext: Improve test coverage #130197
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.
It's actually a bit strange that an input file is not required.. maybe it should?
It should, and output should only be generated if there are msgids, but that is beyond the scope of the pr. I can open an issue for the discussion of this. |
Definitely, I just found it surprising looking at the test and wondering where the input file is 😄 I think the input file should be required, could you open an issue? |
This comment was marked as resolved.
This comment was marked as resolved.
How is it broken? It outputs to stdout, no? |
This comment was marked as resolved.
This comment was marked as resolved.
Thanks @StanFromIreland for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
(cherry picked from commit e5e51bd) Co-authored-by: Stan Ulbrych <[email protected]>
GH-133266 is a backport of this pull request to the 3.13 branch. |