1) contrib.admin places jQuery in its own namespace `django.jQuery`. In this way other jQuery instances should not conflict with it. 2) It also removes the dollar sign AND the `jQuery` object from the global scope.
*I think* removing the `jQuery` object is not necessary because it *should* not conflict with any other jQuery instance. If an admin customization that uses jQuery is loaded, as it should, after the contrib.admin's javascript, its `jQuery` object will override the django's one, and django will still be able to use jQuery with `django.jQuery`. If an admin customization is loaded before the contrib.admin's javascript, it *should not* work anyway even if we removed jQuery from the global scope. That's because jQuery.noConflict(true) removes the jQuery object from the global scope, but doesn't prevent it to be created and attached to window (thus overwriting the user's one). Moreover I wont' be able to use any jQuery plugin (that directly references `jQuery`) in the admin (without hacking with ModelAdmin._media), because the `jQuery` object does not exist. I am forced to include jquery twice ... -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
