Max Battcher wrote: > gabor wrote: >> i actually got around this problem by adding the project-dir to the >> PYTHONPATH, but it seems a little as a hack... > > I'd have to disagree. I don't think it's a hack at all, as far as I'm > concerned it makes sense if you think of the project directory as a > "library namespace"
i see... my problem is then maybe... a phylosophical one.. how to explain.. i have a bad feeling when i'm doing something differently than the official tutorial :) it makes me feel that i'm doing it not the django way :) or to formulate it differently: why is the tutorial doing it the way it does? wouldn't it make more sense to do it the project-dir-on-pythonpath way? > (you don't expect the django framework itself, or > any other Python library, to drop their namespace when you start using > them in your own project, do you?). > could you explain this in a little more detail? (it's 00:26 already here, so i'm not the brightest right now ;) thanks, gabor --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
