On Jun 2, 9:51 am, batiste wrote:
> What about the problem that you can, in theory, use the same
> application several time (several instance) within the same project?
There is a Google Summer of Code Project
http://code.djangoproject.com/wiki/SummerOfCode2010
that will hopefully take care of th
> >> By playing around in a python session it seems that the call to the
> >> system randrange with random.SystemRandom().randrange(0,
> >> _MAX_CSRF_KEY) never stops (or doesn't seem to stop in less than 30
> >> minutes) whereas a call to the "normal" randrange with randrange(0,
> >> _MAX_CSRF_KE
Hi Hejsan,
we discussed this topic at the sprints of DjangoCon.eu some time ago.
There is a page in the wiki for this topic where we summarized some
ideas:
http://code.djangoproject.com/wiki/ModelInterNationalization
Instead of one of the existing solutions (which all have serious
drawbacks), I a
Hi,
> 1. You have an object for each language. This object contains some
> language-attribute which makes it easy to filter stuff. Admin and views
> are no-brainers.
I think this is the right approach. A sample API is open for
discussion here:
http://code.djangoproject.com/wiki/ModelInterNational
Hello,
I guess the most interesting point in this discussion is:
> After a while that I spent time to develop new tags and filters
> especially for
> new projects, I began to think a way to implement a template engine
> that
> would let me no more write sort of "plugins" like tags and filters, a