On Fri, Apr 16, 2010 at 12:23 PM, Tom X. Tobin wrote:
> None of this means that I think the core development process should
> change. (Well, besides my fervent desire that they officially adopted
> git — and yes, I do believe it *would* make a difference, centralized
> "official" branch and all —
On Fri, Mar 19, 2010 at 11:09 AM, Karen Tracey wrote:
> However, it does seem to be in direct conflict with the idea of getting to
> the ORM working on non-SQL databases. The additional methods mentioned
> (select, from, leftJoin) together all sound like they are moving the app-ORM
> interface clo
> PS: Can people *please* use 'cls' and not 'klass'. =/
Yes you are right, my fault. Although I did just rip the code from
the patch at http://code.djangoproject.com/ticket/2659 and modify it.
Additionally, looking at that issue will likely give some insight into
the response this change will li
Seems like it'd be pretty simple for the developer to make a little
helper method like so...
>>> def latest_or_none(klass, *args, **kwargs):
>>> try:
>>> return klass.objects.filter(*args, **kwargs).latest()
>>> except klass.DoesNotExist:
>>> return None
I guess I don't se
I think umovi makes a great point here when he mentions that templates are
often used for things that are not HTML. "Be decoupled from HTML" is one
of the core design philosophies listed in the docs.
I'm not really advocating for or against adding a truncate filter, but I do
think that "you shou
I'd love to see this change get put in. I think the most common case
for forms is to trim whitespace, not the other way around. I'd rather
have the extra work come in for the rare case (when you wanted to
preserve leading/trailing spaces).
-Taylor
On Oct 10, 11:37 am, Barry Pederson wrote:
>
