> > > It does introduce the added overhead of changing all your "import" > statements every time you modify your module, however. >
RE: changing: That is undesireable (especially when thinking of clients) - so, instead, it implies a need for some standard, automated way. It seems that import modules.some_name would need to handle some special behavior w/in web2py. The first thing that comes to mind is a registry that matches a app/version with the latest module/version (the first time), and then announces when there's something new (a possiblity to upgrade)... This _might_ need to look like web2py.import modules.somename... It doesn't really matter - at this point this seems to me more like "requirements gathering", and less like "implementation brainstorming"... Regards, Yarko --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
