#10928: BooleanField: different behaviour when default=callable
----------------------------+-----------------------------------------------
 Reporter:  a...@gc-web.de  |       Owner:  nobody    
   Status:  new             |   Milestone:            
Component:  Uncategorized   |     Version:  SVN       
 Keywords:                  |       Stage:  Unreviewed
Has_patch:  0               |  
----------------------------+-----------------------------------------------
 When using a callable, the behaviour of the BooleanField is different from
 just using a constant. Example:
 {{{
 foo = models.BooleanField(default=lambda: False)
 }}}
 vs.
 {{{
 foo = models.BooleanField(default=False)
 }}}

-- 
Ticket URL: <http://code.djangoproject.com/ticket/10928>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to