>I'm sure people are convinced I'm just arguing for the sake of it, but I >really am trying to get across a point which just hasn't been addressed >by people who want to be toolkit-agnostic to the max.
I think we should be as toolkit-agnostic as we are templatesystem-agnostic and ORM-agnostic. We deliver one with Django, and all Django code builds on the delivered ones. But we don't enforce those on users, if they want to use something else. So just select one for the Django admin stuff and build stuff around that one. But just keep in mind that things should at least have lower-level APIs that could be used even if the selected toolkit isn't used itself, but some other toolkit is. Sure, people won't be able to use all aspects of Django when switching toolkits - but that's the same with ORM and template system, you just can't use all aspects of Django when switching them to SQLObject or Cheetah. bye, Georg
