On Jun 12, 8:56 am, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> I suspect that if I saw a working patch I might lean a
> bit more towards +0, but it's pretty low on my radar.
Ok, I attached a patch. The funny thing is that that use-case sounded
good but it won't work due to how {% for %}
On 6/11/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> Anybody else who isn't James or SmileyChris (since they've spoken in the
> tickets) got a strong opinion either way?
I had a bit of a conversation with SmileyChris about this in IRC
recently, though that was before this use case came
Hello Henrik!
(I think this has to do with what you're trying to accomplish, correct
me if wrong ;) In terms of keeping cache synced with data in models,
this is something I'm trying to address with my GSoC project for the
summer[1]. In fact, the current code already has a mechanism for
tracking
On 6/11/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> I don't want to start an opening/closing battle in Trac, so I'll bring
> this up here: I'm almost convinced by the use case for adding "else" to
> "ifchanged" in #4534.
>
> It's admittedly very borderline and on another day I could see
All the other IF* tags have else clause, I see no reason why ifchanged
should be alone without it.
I say +1 for consistency
On 6/11/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> I don't want to start an opening/closing battle in Trac, so I'll bring
> this up here: I'm almost convinced by
I don't want to start an opening/closing battle in Trac, so I'll bring
this up here: I'm almost convinced by the use case for adding "else" to
"ifchanged" in #4534.
It's admittedly very borderline and on another day I could see myself
saying this is programming with templates. But for some
Just wanted to mention that the issues Malcolm brought up here have
since been resolved, and I believe the branch is ready to be merged:
1) Many backends.supports_tablespaces checks: we decided to leave this alone.
2) Backwards incompatibility with truncate_name use: this has been
fixed by
On 6/11/07, Don Arbow <[EMAIL PROTECTED]> wrote:
> Did you search Trac? This looks like it's already been proposed and a
> patch submitted:
>
> http://code.djangoproject.com/ticket/2066
Yeah, I tried that code and found it pretty poorly written and full of
bugs. Looks like I didn't note that on
2007/6/10, Brian Harring <[EMAIL PROTECTED]>:
> Curious, how many folks are actually using dispatch at all?
I use signals this way:
http://groups.google.com.mt/group/django-users/browse_thread/thread/dcc8ed4b26fd261c/12a19040ad7af699?lnk=gst=2#12a19040ad7af699
and it can be useful too when you
On Mon, 2007-06-11 at 13:01 +0300, Noam Raphael wrote:
[...]
> I did a fresh SVN checkout, and made a new project, and run
> ./manage.py shell, and got:
>
> [EMAIL PROTECTED]:/tmp/mysite$ ./manage.py shell
> Python 2.5.1 (r251:54863, May 2 2007, 16:56:35)
> [GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)]
Ok, I posted my patch at http://code.djangoproject.com/ticket/4529
On 10/06/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> By the way, one advantage of writing the functionality you want as an
> extra tag (something not called "block") is that you (or anybody else
> who wants to work this
On Sun, 2007-06-10 at 09:07 -0700, Brian Harring wrote:
> Curious, how many folks are actually using dispatch at all?
>
> For my personal usage, I'm actually not using any of the hooks- I
> suspect most folks aren't either. That said, I'm paying a fairly
> hefty price for them.
>
> With
On Jun 1, 2007, at 8:34 PM, kernel1983 wrote:
> I've write a session middleware myself instead of contrib.sessions. It
> uses memory instead of database. But it can be used only in dev mode
> just like the cache's simple backend.
Did you search Trac? This looks like it's already been proposed
On Sun, 2007-06-10 at 15:23 +, [EMAIL PROTECTED] wrote:
> I've filed a ticket on this as well: http://code.djangoproject.com/ticket/4520
I'm not quite sure what result you are expecting from a ticket like
that, though. It doesn't contain any sample implementation or even a
proposed API, so
On 6/10/07, John D'Agostino <[EMAIL PROTECTED]> wrote:
> Would one of the core devs comment if this on the right track?
Sounds about right to me; I'd love to see the code!
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
15 matches
Mail list logo
