#24500: Django runtests - 3 tests fail on windows due to encoding troubles
--------------------------------------+------------------------------------
Reporter: pakal | Owner: nobody
Type: Bug | Status: new
Component: Internationalization | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by pakal):
Hum I tried different ways of catching decoding exceptions to provide a
fallback, but it broke more tests elsewhere....
In the end, I just special-cased the "xgettest -V" call, which doesn't
respect utf-8 encoding, and let the rest encode/decode as is (CF attached
patch). Tested on windows 7, on latest python2 and python3 interpreters.
In the patch I also added some encoding details to an error message (to
help, since encoding troubles are recurring), but maybe it's too much
information, I don't know.
I'm amazed, though, that xgettext, which is supposed to deal with
internationalization, doesn't provide parameters to controls its output
encoding, doesn't say anything about it in its docs (afaik), and has
different stdout encodings in its different commands...
--
Ticket URL: <https://code.djangoproject.com/ticket/24500#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.9c84cbdf7c4730cd00a9b3ac07a73587%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
