Opened 6 years ago

Closed 6 years ago

#17509 closed Bug (wontfix)

Project-level locale directory is not found when project is in a nested module

Reported by: anonymous Owned by: nobody
Component: Internationalization Version: 1.3
Severity: Normal Keywords:
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


We have a Django project in a nested module structure, it looks something like this:

So our project-level locale is in


And is:


The documentation states:

  1. Then, it looks for a locale directory in the project directory, or more accurately, in the directory containing your settings file.

But the code takes the first level of the module structure:

Therefore the locale directory is being looked for here:


There is a workaround in that the path can be explicitly set in settings.LOCALE_PATHS.

Change History (2)

comment:1 Changed 6 years ago by Ramiro Morales

Triage Stage: UnreviewedDesign decision needed

(See also

That's precisely the reason why deprecatd the project-level locale directory concept in 1.3. See

I don't think it would be worth fixing this for Django > 1.3 since we are going to remove this support completely in Django 1.5 (or more precisely, Django 1.3 + 2) and, as per our backports policy, an hypothetical fix wouldn't ever reach 1.3.x (the version the OP is using).

Suggestion for the OP: Stop using the project-level locale and swtich to lisitng thedirectory in LOCALE_PATHS as you've already discovered.

Setting design decision needed to get more opinions.

comment:2 Changed 6 years ago by Claude Paroz

Resolution: wontfix
Status: newclosed

I was just going to close it as wont't fix. So just doing that !

Note: See TracTickets for help on using tickets.
Back to Top