Re: [GSoC composite fields] Late post-GSoC check-in #1

First off, let me apologize for not reporting progress after the SoC has ended. At first I thought I'd relax for a few days, but then the work started piling up and I think anyone can guess how it went from that point on... So, again, my apologies. Second, I want to say a big thank you to the

Re: How to do equivalent of LEFT JOIN ON in Django (returning all Left rows, when Right item may not exist)

On Sat, 8 Oct 2011 16:30:37 -0500 Javier Guerra Giraldez wrote: > On Sat, Oct 8, 2011 at 8:18 AM, Michal Petrucha > wrote: > > Behind the scenes, Django does a JOIN. Its type (INNER od LEFT OUTER) > > is decided based on whether the left-hand column

Custom transform in django docs

Hi all, Django currently uses a custom transform class when building docs using Sphinx. What this does is attempt to find blockquote elements and pull their contents up a level, discarding the now empty blockquote element. The reason for this appears to be that it allows you to write

Re: Shouldn't views.generic.create_update.lookup_object use the default manager instead of .objects?

It is indeed a bug. On Fri, Oct 7, 2011 at 10:19 AM, Guilherme Salgado wrote: > Hi there, > > That function uses .objects on whatever model is passed to it by > update_object() (or delete_object()), and I can't think of a reason to > use that instead of the default manager