There is a bug in django which leads to getting the same cache output
for different subdomains (but same PATH) - eg. pl.example.com/test/
and en.example.com/test/ . I've filled in BUG here:
http://code.djangoproject.com/ticket/15978
As aaugustin wrote, there are two ways of implementing:
- reques
On 09/05/11 16:22, fission6 wrote:
> Is there a way to re-factor the CBV approach so that templates simply
> get an instance of the CBV rather than trying to tweak context as well
> as having template context loaders like user and what not?
>
> it seems there'd be a way in CBV to simple push the c
Hi guys,
I spent literally *months* trying to find the best way to resolve this
situation. On our high performance sites + backends (around 120qps, 50/50
split between read and write) we were getting IntegrityError raised by
get_or_create (which we now refer to as Object Collisions).
We are able
Currently there are at least 4 open tickets [1-4] that propose the addition
of new lookup types. Two of them [1,2] are in DDN because of backward
compatibility concerns.
Following that (IMHO valid) logic makes it impossible to _ever_ add new
lookup types to django without breaking backwards comp
Is there a way to re-factor the CBV approach so that templates simply
get an instance of the CBV rather than trying to tweak context as well
as having template context loaders like user and what not?
it seems there'd be a way in CBV to simple push the caller instance to
the template where you'd ha
Hi all,
This may be a bug in Django.
We have a lot of forms and datetimefields. Apparently, DateTimeInput
objects are initialized right after the first page load of the server,
where self.format for this instance is set according to the current
language.
DateTimeInput._format_value, which is call
