On 3/7/06, Ian Bicking <[EMAIL PROTECTED]> wrote: > For this file in particular I don't see any problem with Python syntax, > or even a funny Python-like syntax (i.e., exec in a funny namespace -- > though I'd be sure to test that in 2.3, since it acts differently on > this stuff I think). At least as it isn't advertised as a Python module > through the .py extension. Then it's just a matter of aesthetics. Of > course, if it is aesthetics then that's a good sign that you can waste > an unbounded amount of time. Maybe just do whatever now -- use what you > have with a new extension -- and add another file extension later if you > come to hate what you've made ;)
The fact that there is an aesthetics aspect to this is evidenced by the subject of the thread :) In the end, I need to make a choice. The purpose of the thread is to just get a feel for what others think rather than choosing in my own little vacuum. > I feel more strongly that external configuration should be simple (and > ConfigParser keeps things pretty simple, even when you might wish it > didn't). But I feel even *more* strongly that external and internal > configuration should be kept separate, so I kind of like if they use two > different syntaxes. I agree that things need to be simple, and my intention is certainly not to have Python code leaking into the config file. At the same time, I'd like to be sure that people can do simple computations as required to get things configured correctly (0.9 specifically needs to do an absolute path computation. I could, conceivably, do that in a post-processing step, though.) I'm definitely in agreement that external and internal config are separate (app vs. deployment config), and I'm glad we made that change in TG 0.9. I prefer that they're the same kind of file, though. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
