Fixed #26692 -- Relaxed an i18n compilemessages test.

The actual non-ASCII character differs on Windows.
This commit is contained in:
Ramiro Morales 2016-06-01 10:20:57 -03:00 committed by Tim Graham
parent db2a6b6bfa
commit 71421e8f87
1 changed files with 2 additions and 2 deletions

View File

@ -178,12 +178,12 @@ class CompilationErrorHandling(MessageCompilationTests):
try: try:
call_command('compilemessages', locale=['ko'], verbosity=0) call_command('compilemessages', locale=['ko'], verbosity=0)
except CommandError as err: except CommandError as err:
self.assertIn("'<EFBFBD>' cannot start a field name", six.text_type(err)) self.assertIn("' cannot start a field name", six.text_type(err))
else: else:
cmd = MakeMessagesCommand() cmd = MakeMessagesCommand()
if cmd.gettext_version < (0, 18, 3): if cmd.gettext_version < (0, 18, 3):
raise unittest.SkipTest("python-brace-format is a recent gettext addition.") raise unittest.SkipTest("python-brace-format is a recent gettext addition.")
with self.assertRaisesMessage(CommandError, "'<EFBFBD>' cannot start a field name"): with self.assertRaisesMessage(CommandError, "' cannot start a field name"):
call_command('compilemessages', locale=['ko'], verbosity=0) call_command('compilemessages', locale=['ko'], verbosity=0)