Daily Life in an Ivory Basement

OK Folks, I know that planet.python.org and planetpython.org underwent a merger, and during the merger a new, or patched, or somehow upgraded version of planet went into effect on both. However, I cannot find a link to the info post any more.

I would like to put the latest stable version of PlanetPlanet into effect on the Google Summer of Code/Python site but I am wary of using the devel repo without any inside info. (I am currently running 2.0, which is the latest official release.)

Should I use the dev repo, or should I track down whatever version planet.python.org is using?

thanks!

--titus

Tracy recently asked me if there were any good guidelines about how to write configuration files -- not coding-level guidelines, but guidelines on structure and content.

I was unable to come up with anything: my Google-fu failed me, and my DevonThink database was silent (although it did have some nice testing articles, which I of course forwarded on to her).

I must admit to a general mental block on the subject of how to write config files. How do you choose the right balance between configurability and complexity? What about language -- should they be native Perl/Python/whatnot (Tracy's package is for programmers) or is there a benefit to embracing the mental overhead of config file parsing?

Thoughts and pointers appreciated, either in comments or via email.

--titus