If you use django-localeurl, you might run into the issue that on some machines, django.core.urlresolvers.reverse() works just fine and returns a URL with the locale prepended, while on other machines, it does not.
The reason is that, when localeurl is installed, it monkey-patches django.core.urlresolvers.reverse to change its behavior and have it prependÂ a locale to whatever URL is to be returned. And what happens is that the load order of the different files Django needs can change from one machine to another, thus makes the monkey-patching occur at a different timing, and you end up importing on some occasions the unpatched version of reverse().
The real solution, according to the localeurl author themselves, would be to devise a solution for localeurl which doesn’t involve monkey-patching at all.
Until this is done, here’s a work-around that works, even if a bit ugly.Â Instead of:
from django.core.urlresolvers import reverse ... reverse('xyz')
Try this, ï»¿you’ll make sure you always get the patched version:
from django.core import urlresolvers ...urlresolvers.reverse('xyz')