On 5/18/07, Jason Davies <[EMAIL PROTECTED]> wrote: > Is there any way around this, or is it just something inherent to > Python?
Personally, I think the sanest way to handle a standalone app is to assume it'll be directly on the Python path and build around that idea; asking people to install into specific locations feels a bit weird, and if you do distutils you end up directly on the Python path anyway. If an app later gets added to django.contrib, it can be committed in there after a search-and-replace on its imports, of course :) -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
