2009/7/2 小谢 <[email protected]> > > > > On Jul 2, 4:55 pm, Yarko Tymciurak <[email protected]> wrote: > > On Thu, Jul 2, 2009 at 2:19 AM, 小谢 <[email protected]> wrote: > > > > > On Jul 2, 2:30 am, Yarko Tymciurak <[email protected]> wrote: > > > > On Wed, Jul 1, 2009 at 9:19 AM, Сл <[email protected]> wrote: > > > > > > ...... > > > > > > > Thanks. It really helped. It's lucky that the project is still in > its > > > > > early stage and we'll be refactoring the existing code with respect > to > > > > > web2py's conventions. > > > > > > Glad it helped. > > > > > > Of course, you do not need to import for every request (overhead) if > you > > > use > > > > your utility only sometimes.... > > > > > > then, you can just import the module / utility locally, where (and > when) > > > > it's needed. > > > > > In .py files in models directory, "__all__" doesn't work, does it? > > > > I think you mean something like: > > > > from applications/my_app/util import * > > > No, I mean, for example, there are three classes A, B, C in models/ > 0.py. Then these three classes are visible in the global MVC > namespace. You have no means to prevent the other model/control class/ > func from using them and there is risk of potential name collision > (custom class A vs web2py's html class A), right?
I think you would have to check this yourself, programmatically. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
