On 5/28/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > My understanding of the module is that it doesn't enforce rules and > procedures and that is certainly what I think of policy as being,too.
Your understanding is correct. It doesn't do any enforcement of any rules, but simply provides values that can be used to do so within your own code. I admit that the term "policy" does seem a little far-reaching, but it seems (to me) more specific than anything I'm come up with so far. > I'm not in love with that name. Something based around "values" or > "parameters" is going to be more self-descriptive, I feel. Yeah, things like "values", "paramters", "options", etc. are definitely more self-limiting, preventing it from overstepping its functional boundaries. I guess the real problem here is the trade-off between accuracy and informativeness. There's a valid argument against "values" because it doesn't immediately describe what it is or how it's useful, while you also raise a valid argument against something like "policy" because it overstates what the app can actually deliver. Maybe a combination of the two would be a bit better. "policyvalues"? Indicating its usefulness in the scope of policies while still being clear that its features only extend to the values. I dunno, I'm stumped. -Gul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
