On Dec 15, 2009, at 11:16 PM, "Sean O'Connor"  
<[email protected]> wrote:

> In regard to the deferred fields option, I'll let Jacob speak for  
> his view but I've approached such functionality as "nice to have"  
> for the patch since its not critical to the patch being useful.   
> Personally I haven't had the time to figure it out and implement it  
> so my original patch didn't include it.

I like the idea of the deferred fields, but if we don't implement it  
now, people may come to rely on the AttributeError so that we can't  
add deferred later. Perhaps a note in the docs stating our intent to  
add deferreds would suffice?


--

You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.


Reply via email to