On Nov 18, 5:43 pm, Ludvig Ericson <[EMAIL PROTECTED]> wrote:
> Isn't that a generic view?
Yes. It's built into Django and already does exactly what some people
want render_to_response to do, so why all the hullabaloo? (Or am I
still missing something?)
Out of curiosity, for those who want RequestContext added to
render_to_response, is there a reason you don't like using
direct_to_template instead? I see the two as being functionally
equivalent (minus the addition of RequestContext, of course), but this
debate crops up every so often -- is there
On Sep 10, 11:04 pm, Tai Lee <[EMAIL PROTECTED]> wrote:
> I'd like to propose a `create_or_update` method, similar to
> `get_or_create`
FYI: there is an old ticket (with patch) for this called
update_or_create [1].
.. [1] http://code.djangoproject.com/ticket/3182
On Jun 25, 4:58 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> I'm setting up sprints leading up to the 1.0 release, and I need some
> volunteers to host a couple of 'em.
>
> So we need a spot for 8/1, 8/15, and 8/22 -- any takers?
It's just out of your date range, but the Utah Open Source
For the record, this issue really bothered me too until I found
direct_to_template. Now it is a non-issue.
On Jun 11, 1:22 pm, Gabriel Farrell <[EMAIL PROTECTED]> wrote:
> It's fairly clear that we're setting
> up a dictionary of variables for the template, pulling data from the
> Profile model.
On Jun 7, 5:17 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> Newforms-admin needs to get done. Putting it off from the first couple
> betas or RCs will just increase the temptation to put it off further,
> so what we should do is identify anything that's slowing it down and
> work to resolve
On Dec 26 2007, 2:50 pm, jdetaeye <[EMAIL PROTECTED]> wrote:
> The implementation is not based on customizing the admin, but
> implementing a generic view with very similar capabilities as the
> django changelist view. In all, around 800 lines of code.
Johan, that screenie looks very nice. Any
> Nathan, perhaps you can post a short excerpt of your code?
>
> Closures are lovely and all, but newforms needs a few minor but
> important design changes so it doesn't require us to do anything even
> slightly hackish. It's close, but no cigar - yet.
I'd be happy to, however if you feel that
> If your verification logic wants to know what field is verifying now,
> you can use closure.
> It is simple, Pythonic and doesn't change core :-)
Closures; fantastic. The more I learn about Python the shorter and
shorter my code gets. :-)
Thanks very much for posting this, Vsevolod. I was
