On 12/24/06 5:04 PM, [EMAIL PROTECTED] wrote:
So then, in order to access a content type, I would have to import the
ContentType instance, and call a function.
That's correct.
It's much easier for our
uses to have an inherited function, or property, on a model to use it.
Again, I'm sorry that's the case -- I really am! However, as a developer of
Django itself I have to keep the design of the framework in the forefront, and
as much as I'd like to save you a line of code, if it damages the overall
design I just can't approve of it.
Luckily, this is open source; you should always feel free to patch Django
itself if your needs don't mesh with those of the designers; that's a much
more effective use of your time than trying to change our minds.
When we mark a ticket "wontfix", we don't do it reflexively; only once we're
sure we don't want to implement a certain feature. That is, "wontfix" doesn't
mean "we're not gonna fix this because we're lazy or don't have time", it
means "we're not gonna fix this because we've evaluated the greater impact on
Django itself and decided that this feature negatively impacts the framework."
Again, I truely wish there was a way we could make everyone happen, but if we
said "yes" to every feature request, well, Django would be in danger of
turning into PHP.
And I know we all don't want that to happen!
Jacob
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
