I'm in favor of the patch you've provided, Luke. Raising an exception seems
like the best option here to me.
While it *is* a logical error to get the related objects of an unsaved
instance, the current behavior seems buggy and (as Ian Clelland points out)
it can be potentially harmful.
FWIW, I'm almost certain Russ's original wontfix was based on the same
understanding we all had upon first reading the ticket. It was only when I
tested it myself that I saw the behavior the OP was really trying to
describe.
All the best,
- Gabriel
--
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.
