On 02-Jun-08, at 11:59 PM, Huuuze wrote:
> I'm new to Django, so please be gentle. Basic question: when > developing a web app, I've typically created an "includes" directory > which stores commonly used functions or methods. From a best practice > standpoint, is it recommended that I create an "includes" directory > (not application) within my project? If so, I'm guessing I can > reference it as "myproject.includes". > > Please let me know if this approach is frowned upon in favor of some > other paradigm. If so, can you show me an example of the preferred > method? there is no preferred method or best practices for directory structure - you may put anything anywhere on the filesystem as long as you give django the correct path to the directory. -- regards kg http://lawgon.livejournal.com http://nrcfosshelpline.in/code/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
