On Sun, Nov 28, 2010 at 3:14 AM, Christophe Pettus wrote:
> Hi, all,
>
> Right now, Django's auth system pretty much uses sha1 hardwired in
> (literally, in the case of User.set_password) for the hash. For a discussion
> of why a general-purpose hash function is not the best idea in the world f
Hello,
This is a proposal related to ticket 10427: Bound field needs an easy
way to get form value [1].
Ticket #10427 is already closed as fixed, but the fix is only partial.
It is now possible to get the value from BoundField, but the value
might be a DB primary key or something else not usable
On Mon, Nov 29, 2010 at 9:27 PM, Bita Bita wrote:
> My client is in a immediate need for a front end engineer whi knows
> Django, Python, AJAX, and/or html5 . This is a full time position with
> a really good pay in Palo Alto, CA. Sent me your updated resume if
> interested.
You're on the wrong
On Thu, Nov 18, 2010 at 9:47 AM, Russell Keith-Magee
wrote:
> However, given the Unless Jannis is willing to downgrade his -1 to a
> -0, I think a BDFL judgement is called for here.
Let's go with {% with a=foo b=bar %}.
Jacob
--
You received this message because you are subscribed to the Googl
--- On Tue, 11/30/10, Jacob Kaplan-Moss wrote:
From: Jacob Kaplan-Moss
Subject: Re: Ticket #7817: Extending "with" and "include" tags.
To: django-developers@googlegroups.com
Date: Tuesday, November 30, 2010, 10:38 AM
On Thu, Nov 18, 2010 at 9:47 AM, Russell Keith-Magee
wrote:
> However, gi
Hello List!
I'm working on queries on embedded objects for Django-nonrel (more
precisely, djangotoolbox) that will use JOIN-like syntax.
For this, I need to know how to distinguish
.filter(spam__op=eggs, foo__op=bar)
from
.filter(spam__op=eggs).filter(foo__op=bar)
in the .where tree used
On Wed, Dec 1, 2010 at 4:34 AM, Jonas H. wrote:
> Hello List!
>
> I'm working on queries on embedded objects for Django-nonrel (more
> precisely, djangotoolbox) that will use JOIN-like syntax.
>
> For this, I need to know how to distinguish
> .filter(spam__op=eggs, foo__op=bar)
> from
> .filter(
On Tue, Nov 30, 2010 at 4:22 AM, Tom Evans wrote:
> First comment is that Django already has a pluggable authentication
> stack, which already allows for this - simply define a new auth
> backend that tests the password in the manner you wish.
My understanding of the pluggable authentication sys
On Nov 30, 9:34 pm, "Jonas H." wrote:
> Hello List!
>
> I'm working on queries on embedded objects for Django-nonrel (more
> precisely, djangotoolbox) that will use JOIN-like syntax.
>
> For this, I need to know how to distinguish
> .filter(spam__op=eggs, foo__op=bar)
> from
> .filter(spam__
Just for the record: I'm with Ivan here and think that
from django.template.response import TemplateResponse
def my_view(request):
return TemplateResponse(request, 'foo.html')
is worse than
from django.shortcuts import render
def my_view(request):
return render(request, 'foo.html')
I th
10 matches
Mail list logo
