[Django] #21229: Cygwin's gettext causes test failure
Django
--------------------------------------+--------------------
Reporter: marfire | Owner: nobody
Type: Uncategorized | Status: new
Component: Internationalization | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
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 [http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/ here]
(as [https://docs.djangoproject.com/en/dev/topics/i18n/translation
/#gettext-on-windows 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...
--
Ticket URL: <https://code.djangoproject.com/ticket/21229>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: marfire | Owner: nobody
Type: Uncategorized | Status: closed
Component: | Version: master
Internationalization | Resolution: wontfix
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by timo):
* status: new => closed
* needs_docs: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/21229#comment:1>