pyblosxom 1.4 and python 2.5
"Will Guaraldi" <[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.user |
|---|---|
| Message-ID | <[email protected]> |
After some weird reports from people regarding PyBlosxom dying when trying to find the datadir key in the config dict, I looked into the issue further and discovered that I borked the WSGI handling code. The good news (if you can call it that) is that it only affects people who are running PyBlosxom on Python 2.5 and people who have wsgiref installed. The bad news is that I shouldn't have borked it in the first place. There are a couple of other minor issues in PyBlosxom 1.4. I'm leaving for Oregon on Friday, though, so I'm going to try to fix all the issues we've discovered so far and do a PyBlosxom 1.4.1 release. After that I'm going back to doing PyBlosxom 2.0 work which involves a lot of code re-writing because some of the stuff we have in there is silly. My apologies to anyone who's bumped into this problem. I'll get out a fix as soon as I can. /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/