2.0 planning and specification
will <[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.devel |
|---|---|
| Message-ID | <[email protected]> |
I added a specification regarding markup for property values when using Paste and blog.ini. I also implemented it. I made some changes to the blosxom_handler and the blosxom_file_list_handler and I added a sortlist callback. Earlier in the week I started writing tests for run_callback. This is the function that a large portion of PyBlosxom relies upon, so it's probably a good thing to have unit tests for. As far as I can tell, I'm the only one looking at the specifications and/or working with them. If you need things added/removed/changed for 2.0 and you're not joining the discussion, then you're going to miss the boat. I don't mean to scold anyone--just giving fair warning. I'd like to get a solid PyBlosxom 2.0 out the door before the end of the year. /will ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/