Opened 12 years ago
Closed 12 years ago
#21229 closed Uncategorized (wontfix)
Cygwin's gettext causes test failure
| Reported by: | Kevin Christopher Henry | Owned by: | nobody |
|---|---|---|---|
| Component: | Internationalization | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I was getting the following error while running the test suite on Windows:
======================================================================
FAIL: test_comments_extractor (i18n.commands.extraction.BasicExtractorTests)
----------------------------------------------------------------------
Traceback (most recent call last):
File "C:\Django\django\tests\i18n\commands\extraction.py", line 83, in test_comments_extractor
self.assertTrue('#. Translators: One-line translator comment #3' in po_contents)
AssertionError: False is not true
After some investigation I realized that this only happened while using Cygwin's 0.18.1 version of gettext: switching to the Windows 0.18.1 binary from here (as recommended) caused the test to pass.
I'm guessing this has something to do with the handling of line breaks, since I was also able to make the test pass by removing the line break between {% comment %} and Translators: in tests/i18n/commands/templates/test.html. I haven't investigated much further.
So this does not seem to be a Django bug, but I thought I'd mention it...
Note:
See TracTickets
for help on using tickets.
I guess the actionable item would be to document this, but I don't think we can reasonably expect to keep a full list of caveats on all known systems up-to-date, so the wiki is probably more appropriate for this info. Feel free to create a page (or find an existing one) if you'd like.