I think this sounds like an ideal solution to handling common needs and requests that don't belong or aren't wanted in django core/contrib. Over time if certain libs or functions prove esp. useful they could be "promoted" to the distribution if wanted (by core committers).
Just because something doesn't belong in the dist doesn't mean everyone should need to rewrite their own libs for very common tasks... as you look to be doing already this type of approach could be a good solution the AJAX threads -- keep them out of core yet still easily allow people to share work and leverage common solutions. I guess this whole situation sort of happens on its own (other libs being written and adopted) but it could be quite useful to have the effort be more organized and less organic... nice job! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users -~----------~----~----~----~------~----~------~--~---
