Thought I'd add this in case someone searches on this later... I usually do something like:
#### Begin Python Code import sys sys.path.insert(1, module_directory) #### End Python Code at the top of my module. The above puts the module_directory into the current sys.path (aka, PYTHONPATH, but only for the current process) as the second item (right after the '' path) sys.path behaves as a normal Python list, so you can manipulate it any way you like using normal list methods To be clear...This is a basic Python trick...nothing specific to TG. Kevin Horn On 8/1/07, Jim Steil <[EMAIL PROTECTED]> wrote: > > Thanks Florent! > > That (and fixing the path to my dev.cfg) did the trick. > > -Jim > > Florent Aide wrote: > > On 8/1/07, Jim Steil <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> wrote: > > [...] > > ImportError: No module named motion > ______________________________________________ > > Hi Jim, > > could you just try to launch this command in the root of you app (motion) : > > python setup.py develop > > this will make sure the motion package is correctly added to your > python path as if the application was installed in production. > > Cheers, > Florent. > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
