Sorry, but the longer we discuss, the more it becomes clear: Django's
behaviour is certainly wrong.
I'm puzzled how no Django core developer seems to understand it. I hope
that this is just because they are not following this thread because
there is admittedly more urgent work to do right now.
Wi
On 10 fev, 12:42, Luc Saffre wrote:
> Thank you, Henrique, for dropping in.
>
> Django's current behaviour is not correct because it forces me to access
> non-nullable FK fields differently than nullable ones. "In Python,
> throwing exceptions for expected outcomes is considered very bad form"
> [
Anyone looked at this yet?
http://bitbucket.org/izi/django-admin-tools/wiki/Home
http://izimobil.org/django-admin-tools/docs/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegrou
Once again:
This is really not the time to be discussing this; anything in this
thread's going to be long forgotten by the time 1.2's out and 1.3
feature discussions are going on.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You received this message bec
On 10 February 2010 23:33, Sayane wrote:
> I think that an easy way to define your own user model is better idea. Auth
> app should be more generic. It should define a protocol for user, group and
> permission objects /../
Why should permissions and groups be in the same app as the user? Less
reu
On Wed, Feb 10, 2010 at 7:24 PM, Forest Bond wrote:
> Hi,
>
> On Wed, Feb 10, 2010 at 11:09:29AM -0800, mrts wrote:
>> You don't need that fix to use efficient file serving.
>>
>> Just use an empty response and set the X-Sendfile header manually if
>> using
>> Apache. If not, check your server doc
