On Aug 22, 8:12 am, Russell Keith-Magee
wrote:
> On Sat, Aug 22, 2009 at 7:49 PM, Tim
>
> Chase wrote:
>
> > James Bennett wrote:
> >> The current proposal is for a "USPostalCodeField" which
> >> corresponds to the US Postal Service's list of postal codes:
>
> >>http://www.usps.com/ncsc/lookups
On Mon, Aug 24, 2009 at 8:47 PM, Andi
Albrecht wrote:
>
> I've attached a patch to the issue on the tracker. The patch splits up
> the mail module into a package and provides the backend functionality.
> Documented functions and classes are of course available in the
> top-level module. Undocument
On Mon, Aug 24, 2009 at 5:09 AM, Jukka wrote:
>
> Hi all,
>
> I've been working with Django for a bit now, and decided to try
> contributing, by submitting a patch to fix a problem I ran into at
> work. This seems like something that requires a design decision.
>
> So, what do you think?
On the w
I've attached a patch to the issue on the tracker. The patch splits up
the mail module into a package and provides the backend functionality.
Documented functions and classes are of course available in the
top-level module. Undocumented methods like make_msgid() are not
available in django.core.ma
On Mon, Aug 24, 2009 at 9:14 AM, Andrea Zilio wrote:
>
> So the answer to the question "Can I get the right instances with one
> single and only DB query" seems to be:
> "No, you cannot do so without touching the Django orm code".
>
> Am I right?
If, by "one single and only DB query", you mean a
On Mon, Aug 24, 2009 at 1:40 PM, tom wrote:
>
> Hi,
>
> The form_class property for generic views such a
> django.views.generic.create_update.* should accept either a ModelForm?
> class or a ModelForm? object. This would allow generic "wrapper views"
> to easily inject run-time data into the form
