On Mar 27, 2010, at 1:08 PM, Russell Keith-Magee wrote:
> Option 3: We modify the existing signals so we have a pre-post pair
> for every signal. This maintains the analog with pre/post save, and
> gives the most control. For example, on Alex Gaynor has suggested to
> me that some people might wa
On Mon, Mar 29, 2010 at 12:22 AM, Renato Garcia Pedigoni
wrote:
> Hi Alex and Russel
>> * Your schedule is so vague it borders on being comical. I generally
>> use the rule of thumb that if a proposal contains a body of work
>> longer than a week, the person making the proposal doesn't understand
On Wed, Mar 10, 2010 at 5:33 AM, Alex Gaynor wrote:
> On Tue, Mar 9, 2010 at 5:56 PM, Renato Garcia Pedigoni
> wrote:
>> Hi folks
>> My name is Renato, I'm currently studying Biomedical Informatics at the
>> University of Sao Paulo, in Brazil.
>> Last year I tried a GSoC slot with a declarative s
Hi Alex and Russel
First, sorry for the delay, and thank you for reading my proposal and
commenting on it.
* A generic view that works with the serializer is probably a good
> idea, but is orthogonal to the task of building a customizable
> serializer. The serializer should be standalone. If you
However I still believe, as a user of the framework, having 2 signals,
before and after, are the best way to go. It is the most intuitive and clear
way to provide this functionality.
On Sun, Mar 28, 2010 at 4:44 PM, Firat Can Basarir <
firatcanbasa...@gmail.com> wrote:
>
>
> On Sat, Mar 27, 2010
On Sat, Mar 27, 2010 at 8:08 PM, Russell Keith-Magee wrote:
> Hi all,
>
> One of the new features in 1.2 are signals on m2m operations [1].
>
> Recently, Ticket #13087 was opened questioning the order in which m2m
> signals are sent. I'm calling for any comments or opinions on exactly
> how this
Hi,
I found out using i18n with django breaks caching completely.
(reverse proxy & browser caching, that is).
Initially I filed a bug about this [1], But its more complicated that
just a bug. Therefor I post the topic here.
Whats the problem:
enabling django.middleware.locale.LocaleMiddleware,
