Django does not pick up .mo files when LOCALE_PATHS is unset

[Ondřej Kolín]

Update: Kinda resolved, see my comment.

1. Set LANGUAGE_CODE and LANGUAGES in settings.py
2. You are able to makemessages and compilemessages
3. Django is not picking up the translated messages
4. Set the LOCALE_PATHS variable in the settings.py
5. django now picks the messages

Fragment of settings.py

LANGUAGE_CODE = 'en'
LANGUAGES =[ ('en', _('English')), ('cs', _('Czech')) ]
LOCALE_PATHS = (
    os.path.join(BASE_DIR, 'locale'),
)

If this is intended, I think that makemessages/compile messages should fail as well. If not, the discovery should work as well.

Basic dir structure
.
├── db.sqlite3
├── locale
├── manage.py
├── safecloud
├── secshare
└── static

cat ./../venv/pyvenv.cfg
home = /usr/bin
include-system-site-packages = false
version = 3.8.3

[Ondřej Kolín]

Without locales path set

[Ondřej Kolín]

As @felix pointed on irc.freenode.org #django-dev, the behaviour is documented.

But I still think this is kinda bug, or at least inconsistent, because, where is the point to be able to gather messages/compile them, but they stay unusable in the system, because the var is not set.

I think, that ./managepy compilemessages should throw a warning at least.