Since bringing up the topic a few months ago (and getting support for the idea) [1], I haven't had time to whip up a patch to move the contents of various modules' __init__ out into "base" or "main". It finally clicked (you know, several weeks *after* 1.0 features were nailed down, ugh) that this may-or-may-not be such a sane thing to do post-1.0 with a stability freeze. Since I'd like to see non-public API pieces no longer imported back into the __init__ modules eventually (following a depreciation period), I'm curious as to whether others think we can still manage this cleanly post-1.0. If we can, great! — I'll just wait until then. If not, is there any chance we can squeeze this in somewhere?
[1] http://groups.google.com/group/django-developers/browse_thread/thread/35aae0e8da804bd9 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
