On Sep 18, 12:52 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Wed, 2008-09-17 at 14:42 +0100, Ben Ford wrote:
> Parts of it are very well thought out and if it had been a post on "how
> Jinja works" it would have been excellent. Other parts are completely
> unconstrained by facts or
On Sep 19, 9:17 am, Simon Willison <[EMAIL PROTECTED]> wrote:
> On Sep 18, 6:39 pm, Michael Elsdörfer <[EMAIL PROTECTED]> wrote:
>
> > I remember this coming up on django-users and IRC once or twice, and
> > never thought too much about it, but currently, template inheritance
> > and includes
> I've got a workaround for that which works pretty well:
>
> http://code.djangoproject.com/wiki/ExtendingTemplates
Hm I might be misunderstanding, but it seems you're trying to
workaround the situation where two templates might not be uniquely
addressable. I can't quite make the connection to
On Sep 18, 6:39 pm, Michael Elsdörfer <[EMAIL PROTECTED]> wrote:
> I remember this coming up on django-users and IRC once or twice, and
> never thought too much about it, but currently, template inheritance
> and includes don't work together at all:
>
> * Blocks included in a parent template
On Tue, Sep 16, 2008 at 1:57 PM, mrts <[EMAIL PROTECTED]> wrote:
> As for naming, `django.apps` is an arbitrary name, it can be
> `djangoapps` or whatnot. To avoid bikeshedding, core devs could decide
> on that.
>
> Of course, company sub-namespaces are entirely welcome, i.e.
>
On Thu, Sep 18, 2008 at 4:31 AM, laspal <[EMAIL PROTECTED]> wrote:
> I am trying to send mail using sendmail. Getting the error 'unicode'
> object has no attribute 'user'
This question belongs on django-users, not django-development - this
list is for the development of django itself, not usage
I remember this coming up on django-users and IRC once or twice, and
never thought too much about it, but currently, template inheritance
and includes don't work together at all:
* Blocks included in a parent template cannot be overwritten in a
child template.
* Blocks from an include in a child
> Namespace packages and packages living in a namespace are different
> things. I'd say the latter is sufficient.
There are two different name spacing related issues. One is PyPI
organisation, and one is the local one.
Assuming that deployment environments are only set up with the
applications
Hi,
I am trying to send mail using sendmail. Getting the error 'unicode'
object has no attribute 'user'
My view function:
def send_mail(request):
_user = request.user
sender = _user.email
mailing_list = []
if request.method != 'POST':
emailform = EmailForm()
On Sep 18, 7:07 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Wed, 2008-09-17 at 22:19 -0700, mrts wrote:
>
> Keep a handle on the scope. I was going to stay out of this thread until
> some actual code appeared (and I still have a note to re-review Vinay
> Sajip's stuff to remind
On Tue, Sep 16, Malcolm Tredinnick wrote:
> Hopefully there won't be a need to introduce any second attribute here
> (and it can't be called "pks" in any case, since that's the same problem
> as before: by definition alone, there is only one pk on any table/model.
> Calling it by a plural name
On Wed, 2008-09-17 at 22:19 -0700, mrts wrote:
>
>
> On Sep 18, 2:56 am, zvoase <[EMAIL PROTECTED]> wrote:
> > I think the app object thing is a really good idea, but I have to say
> > one thing; why not see if some middle ground can be met between the
> > Django cheeseshop idea (going on in
12 matches
Mail list logo
