You should be able to do the same from the application's /modules folder. Use site-packages if it's a module that needs to be accessed by multiple applications (or possibly by other Python programs).
Anthony On Saturday, December 10, 2011 7:09:32 PM UTC-5, Constantine Vasil wrote: > > Hi Vineet, > > Thank you! Absolutely - you understood my question properly. > It seems that solution is very simple, I am so overwhelmed > with this porting that sometimes I oversee the simplest > solutions ;) > > So if I put it under site-packages like this: > site-packages/models > site-packages/definitions > > I can import them from everywhere > from site-packages.models import models > from site-packages.models import definitions > > and in /models I have: > > class MyClass(db_google.Model) > name = dg_google.string(...) > def profile(self, id) > <some code> > > Then I can the model like this: > > myclass = MYClass.profile(id) > name = myclass.name > > Is that right? > >
