http://code.google.com/p/django-survey/issues/detail?id=9&can=1
Anyone happen to have a strong opinion on this? Should django applications use local imports or package based imports? Sorry if this has been mulled over a million times. pasting conversation here: Comment 2 by doug.napoleone, Today (90 minutes ago) NOTE: The convention is moving to local imports over package named imports for reusable apps. For instance one client of django-survey has all their 3rd party apps under 'externals' and imports those apps as externals.survey.models This means that they have to edit our imports to use the prefix 'externals.' In general when doing package development in python, local imports are preferred over absolute as you do not have control over what 'absolute' actually is. Comment 3 by mandric, Today (76 minutes ago) no shit ... news to me. When I went to the python conference in Chicago this year, all I heard was that local imports are evil. But I guess it all depends. I also thought one of the basic tenants of app development is that the app should always sit on the python path. I wonder what ubernostrum's take is on this because releases (django-registration, django-profiles) use package based imports. And those apps have been around for a long time, he is also a core maintainer and gets paid to work on Django from the what I know. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
