Re: Testing: making it easier to create mock Request objects

On Sep 7, 10:03 pm, akaihola <[EMAIL PROTECTED]> wrote: > I couldn't find a ticket for this issue yet. Simon, mind if I create a > ticket and dump your description of the issue there? Go for it! --~--~-~--~~~---~--~~ You received this message because you are

Re: Testing: making it easier to create mock Request objects

I couldn't find a ticket for this issue yet. Simon, mind if I create a ticket and dump your description of the issue there? -Antti --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post

Re: contrib.auth tests

> > There is a middle ground here, which is that those auth-app templates > > get moved to the Django's main test directory so that they're available > > only to runtests. That doesn't feel particularly self-contained and > > again, for me, violates the intuitive meaning of the word unittest,

Re: Porting from Django 0.96 to 1.0 doc improvement

On Sun, Sep 7, 2008 at 1:10 PM, olive <[EMAIL PROTECTED]> wrote: > > Hello, > > I had hard time to find that I need to add primary_key=True to my > OneToOneFields to make it work as with 0,96. > > I still don't understand why I need add that for 1.0. > > Could you please add some lines about this

Porting from Django 0.96 to 1.0 doc improvement

Hello, I had hard time to find that I need to add primary_key=True to my OneToOneFields to make it work as with 0,96. I still don't understand why I need add that for 1.0. Could you please add some lines about this in the doc ? Thanks again for Django 1.0, Olivier.

Reviews Best Price : Kodak Digital Camera

Kodak EasyShare C713

Re: Forms and edition of an object : non-pythonic default behaviour

On Sep 7, 10:02 am, Tai Lee <[EMAIL PROTECTED]> wrote: > In your hypothetical, how would you handle boolean fields with a > checkbox widget? When they are unticked, they are not included in the > QueryDict. You are quite right. That's a very good reason. Perhaps that HTML should consider a

Re: Forms and edition of an object : non-pythonic default behaviour

In your hypothetical, how would you handle boolean fields with a checkbox widget? When they are unticked, they are not included in the QueryDict. It could get confusing if we start special casing fields like these in order to support "no data" as a different case to "empty data", just to avoid