> This is wandering very far from "should we use setuptools". You are
> talking about a large redesign of the model system towards infinite
> flexibility. That's probably a topic for another thread. It's not really
> tied to setuptools usage beyond you think it would make it easier to
> leverage those changes in the future if setuptools were available (or am
> I misunderstanding?).

That's true. I was just trying to explain my thinking. Let's drop that
example use case, it doesn't really add anything -- one good use for
entry points is enough. :)

> Maybe I'm not being clear: how is setuptools even involved in the case
> of looking for extra database backends?

Backends would be registered by packages as setuptools entrypoints.
Django would iterate the entries in the 'django.db.backends' entry
point to load backends outside of core. This change, requiring only a
few lines, would make it possible for any package to provide a django
db backend. No need for custom loading hooks or enforcing package
naming conventions or anything.

> What does setuptools add to the picture?

It adds the fact that it already exists and works. Entry points provide
a widely-used and well understood way of adding extensibility to an
application. Again, to me, it's a simple build or buy. Why spend time
building something that won't be any better than what you can get right
now, for the low-low price of using ez_setup, something django already
does? After all, we're talking about *dumping* setuptools, not adopting
it. This is a reason not to: it provides this very useful entry points
feature that can be used to support things like pluggable db backends
with very little effort. 

JP


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to