On 11 avr, 07:33, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > If you are integrating a 3rd party library or script into a django (or > ANY python) project, it needs to be available on the python > interpreter's path. It sounds like you are getting hung up on the > mechanics of python's package/module rules. I would suggest > familiarizing yourself withhttp://docs.python.org/tut/node8.html- > particularly the section titled "The Module Search Path". In my > opinion the documentation leaves out a few key points so I would also > recommend reading section 4.1 > here:http://docs.python.org/inst/search-path.html > > Put Django aside for a second, you should be able to fire up a python > interpreter and type>> import <the_3rd_party_module> > > if you have set it up correctly the module will import successfully, > if not you will receive an error. > > Hope that helps. At least it makes sense for me for things I was not aware of. I thought according to the wiki page that Django could make some "introspection" to load any file present in the project in an easy way. I'm not fan of modifying the python path, so as flickr.py do not comme with an installation process, I will put it somewhere in the python path. It's mentionned that python look in current directory but also in python path. What should be the "current directory" for a django project ? the app directory ? the root project's directory ? I'll try these the evening, thanks for the answer ! Nicolas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
