Re: pyblosxom 3000
will guaraldi <[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.devel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 19 Jan 2005, Steven Armstrong wrote: > > As of my understanding the easiest way is to put all shared code into a > module. Then have a "startup-script" for each environment. Similar to > how it's done in Moinmoin. Can you (or someone else) work through the changes that will be involved? The shared code should go into either the pyblosxom.py module or in the PyBlosxom object in the pyblosxom module. We have a common init already--I don't know if that's useful or not for this purpose. I want to fix this for 1.2. > Any direct access to os.environ, sys.stdin, sys.stdout, sys.stderr and > the like should be avoided from within modules/plugins. Ok. Well, we'll figure out the "business rules" involved as we go along. Then we'll document the rules and go through the plugins to see which ones need fixing. > ps: I'll post you a diff regarding the Response stuff. Cool--that'd be super! Thanks! /will ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt