andy's idea works great if you wanted to access your configuration at runtime objects, but i think the OP was requesting it be "not part of the application," so this technique crosses that boundary.
-- wesley - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - "Core Python Programming", Prentice Hall, (c)2007,2001 "Python Fundamentals", Prentice Hall, (c)2009 http://corepython.com wesley.j.chun :: [email protected] developer relations :: google app engine On Jan 9, 10:19 pm, Andy Freeman <[email protected]> wrote: > > > Does any one else agree if the AppEngine environment could provide > > this as a feature, so its not part of the application but rather a > > part of the environment? > > If you make your configuration a db.Model subclass instance, you can > modify it in production without loading a new version. > > That is > class ApplicationConfiguration(db.Model): > debug_mode = db.BooleanProperty() > admin_email = db.StringProperty() > > and so on. > > On Jan 4, 6:30 pm, Devraj Mukherjee <[email protected]> wrote: > > > Hi all, > > > My AppEngine application is written in Python. As the application code > > base becomes larger are experiencing the need to use configuration > > variables for our own applications. Example are we running in Debug > > mode or not, admin email addresses (used to send internal > > notifications) etc. > > > Currently we are maintaining this in a common Python file as varaibles. > > > Does any one else agree if the AppEngine environment could provide > > this as a feature, so its not part of the application but rather a > > part of the environment? > > > Would appreciate comments.
-- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
