id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
25223	Getting DjangoTranslation that doesn't exist should return None	Sander van Leeuwen	nobody	"Getting a DjangoTranslation that doesn't exist used to return None.

Since [https://github.com/django/django/commit/a5f6cbce07b5f3ab48d931e3fd1883c757fb9b45#diff-5682903b7aed1649cdb7095331e90d0d this commit] it raises an IOError when using an unavailable language.

[https://github.com/django/django/blob/a5f6cbce07b5f3ab48d931e3fd1883c757fb9b45/tests/i18n/tests.py#L1344 This test] suggests this is wanted behaviour.

But it should be possible to add a language that is not available in `django/conf/locale/` right?

To reproduce, use a `LANGUAGE_CODE` unavailable in `django/conf/locale/`.

For instance:
`LANGUAGE_CODE = 'sd-PK'`

run `python manage.py validate`

This will raise:
`IOError: [Errno 2] No translation file found for domain: u'django'`"	Bug	new	Internationalization	1.8	Normal				Unreviewed	0	0	0	0	0	0