On 9 juil, 17:42, "Diez B. Roggisch" <[email protected]> wrote: > Am 09.07.2010 um 17:31 schrieb pipoun: > > > Hi, > > > We are using the sqlachemy orm (i.e. the model package) in local stand > > alone applications. > > That's why we want to relocate the package in a completely different > > directory hierarchy. > > > So I'm wondering if I could simply modify the following > > model.__init__.py file to: > > from new.path.to.model.package import * > > > Or is there any other things to watch out? I'm fearing some hardcoded > > paths to the model modules. But as many objects and classes are > > already imported in the original __init__.py we tought it could be > > harmless. > > To say it in german - "probieren geht ueber studieren". Roughly > translated to "just do it". If it fails, try to find out why.
Thanks for the answer, of course I was going to try it, but this behavior could be against some of the TG guidelines, and I don't want to see something break in a few months because I wasn't aware of that. Our TG web app in actually still in dev, and we could add new features that needed some specific stuff in a model's module Cheers > > I guess it should be ok though, all SA & TG care about is that when > importing __init__.py, all model classes are eventually added to the > metadata, especially once the init-function is called. > > Diez -- 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.
