On Sat, 2010-12-04 at 11:56 +0800, Russell Keith-Magee wrote:
> Option 4: Introduce a per-database setting -- TEST_DEPENDENCIES --
> that allows the developer to explicitly encode the dependency between
> databases. This means the developer can explicitly encode the
> dependencies that exists in d
On Sat, Dec 4, 2010 at 8:48 PM, Greg Turner wrote:
> Hi,
> I have a patch for #11930 that in to be applied against djangoproject.com's
> base.css file. As far as I can see, base.css is not in the project
> repository. Who is the custodian of this file, and the other CSS files? Is
> there a reason
You can find it in the community_redux version of the code which will
be deployed any day now.
[0]: https://github.com/jacobian/djangoproject.com/tree/community_redux
On Sat, Dec 4, 2010 at 8:48 PM, Greg Turner wrote:
> Hi,
> I have a patch for #11930 that in to be applied against djangoproject.
Replying to myself here.
I'm quite sure the docs are wrong by now.
Also: I think the documented behavior is not desirable. Changing
translations per-view makes for hard to debug once-in-a-while bugs.
This means the bug '2' is still a problem. I suggest either reversing
the loop
158 for
Hi,
According to
http://docs.djangoproject.com/en/1.2/howto/i18n/#using-translations-in-your-own-projects
and
http://docs.djangoproject.com/en/1.2/topics/i18n/deployment/#how-django-discovers-translations
At runtime, Django looks for translations by following this algorithm:
* First, it looks fo
