Re: #10355 Add support for email backends

On Fri, Aug 21, 2009 at 12:34 PM, Andi Albrecht wrote: > > Hi, > > I'm interested in working on #10355 "Add support for email backends." > > IMHO it's an good idea to make the email backend configurable. There > are at least two use cases I can think of. The first is

#10355 Add support for email backends

Hi, I'm interested in working on #10355 "Add support for email backends." IMHO it's an good idea to make the email backend configurable. There are at least two use cases I can think of. The first is to send email with other services than SMTP, like App Engine as noted in the ticket's

Re: 1.2 Proposal: Add a few more tutorial steps

On Thu, Aug 20, 2009 at 1:03 PM, Nicolas Steinmetz wrote: > Maybe you can inspire from the Jobeet [1] tutorial which consists at the > beginning as an advent calendar (a one hour tutorial published > everyday). Jobeet is a Job board and allow to deal with all aspects of >

Re: 1.2 Proposal: Add a few more tutorial steps

Rob Hudson a écrit : > I'd be happy to help flesh out one or more of these. This isn't > necessarily a 1.2 feature but would be a nice addition to the > documentation. > > If someone already had an idea on these wanted to add some more > details of what to cover under one of those topics, I

Re: Proposal: add static_fields to ModelAdmin

Now that 1.1 is out and proposals for 1.2 are being submitted I decided I would revive this proposal for comments --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group,

Re: Suggestion: Better way to extend user table

Rob Hudson wrote: > Take a look at ticket 3011: > http://code.djangoproject.com/ticket/3011 > > Thanks a lot! That's pretty much exactly what I want. In my opinion this should become a real feature and not just a patch. --~--~-~--~~~---~--~~ You received this

Re: Suggestion: Better way to extend user table

On Thu, Aug 20, 2009 at 9:22 AM, Rob Hudson wrote: > > Take a look at ticket 3011: > http://code.djangoproject.com/ticket/3011 > I don't know, but that seems a little too "magic" for me. The User model appears to be imported from somewhere else than it actually is. Isn't

Re: Suggestion: Better way to extend user table

Take a look at ticket 3011: http://code.djangoproject.com/ticket/3011 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: Inline formsets

On Sun, Aug 16, 2009 at 5:45 AM, mrts wrote: > > At HTML level, a form is a set of fields that gets submitted when > a the form submit button is pressed. > > However, this is not the case with model forms and inline formsets > (e.g. an admin page with inlines) -- inline

Django Sites framework

I'm *not* using Sites framework ('django.contrib.admin' is not included in INSTALLED_APPS and SITE_ID is not defined), but there is an exception when I click on "View on website" link on the edit model page in admin interface. Exception Value: You're using the Django "sites

Re: Django 1.2 proposal: revisit admin autodiscover improvement for custom sites

On Thu, Aug 20, 2009 at 8:36 AM, Brian Rosner wrote: > > > On Aug 19, 2009, at 3:32 PM, Manuel Saelices wrote: > >> This ticket was marked by duplicate of #8500, but I think #8572 >> approach is better (better explicit than implicit). Ticket number is >> not important, but I

Re: Django 1.2 proposal: revisit admin autodiscover improvement for custom sites

On 20 ago, 02:36, Brian Rosner wrote: > On Aug 19, 2009, at 3:32 PM, Manuel Saelices wrote: > > [...] > > I am in agreement the approach in #8572 is best. This has something   > that has bitten me on a few occasions and would like to get this fixed   > in Django. If you are