Re: pyblosxom 1.2 timeline

On 03/04/05 15:47, will guaraldi wrote:
> Ted sent an email regarding the PyBlosxom 1.2 timeline.  I started to 
> reply to that email but then figured it's better off as its own thread.
> 
> The only timeline we have is a "if it's done, then we'll release it" one.
> I think to be done, we'd need the following completed and tested:
> 
>    1. pyblosxom wsgi, mod_python, and other interfaces
>    2. redo the file handling so we can allow for index caching
>    3. pyblosxom i18n
>    4. static rendering fixes
>    5. refactoring of various pieces

    6. a better solution for logging/debugging

> 
> In regards to item 1, I think Steven is still going strong.  It's either
> finished or pretty close to done.  If anyone can try PyBlosxom out in
> these other frameworks, that'd help a lot.
> 

The only issues I'm still having here are the one's with the "config
beeing cached". I'ld say for 1.2 fix that by making a copy of the config
dict in Request.__init__. Then we can figure out how this should work in
the future (1.3+).

Apart from that it all seems to be working. I've tested it successfully
with over 2000 blog entries in the following environments:
python-2.3.4
- apache-2.0.52
  - mod_python-3.1.3
  - CGI
  - wsgi-CGI
- twisted-1.3.0

on the following machines/kernels:
- laptop linux-2.6.10
- two server's running linux-2.4.27 (hardened, grsec)

Maybe someone could test on windooze, I aint got that.

> 
> In regards to item 4, there's a bug (or two bugs) in the bug tracker that
> talk about static rendering problems.  Someone (I think it was Steven)
> mentioned static rendering issues a few months ago.  I don't really know
> where we are with this either.
> 

Static rendering, which I had broken recently, works fine again.

Re: a few months ago:
I only had issues with one plugin, but that was cause the callback chain
is slightly different when using static rendering (The plugin was broken
not Pyblosxom).

Bug 1081492 "Static rendering doesn't work on Windows":
Is fixable I guess. Although I don't understand what's going on there.
IMHO PATH_INFO should never be os specific.

Bug 1081604 "Static rendering doesn't copy non-rendered files":
Is IMHO not a bug. Pyblosxom doesn't know anything about static
resources (images/css/whatever) and therefor can't offer a generic way
to handle them. Or am I missing something?

Bug 1145908 "Using own renderer fails":
The error happens where the headers are removed from the result before
writing out the static files. This code no longer exists as the Response
object handles headers and body seperatly. Mr nobody who reported the
bug will just have to try again with v1.2.

Speaking of bugs:
1103622 "Wiki Access Control Documntation Hard to use":
I posted an answer to the question. Can someone mark this as closed? (it
seems I can't do that)

> And documentation needs work.  I have some stuff half-written that needs
> to be finished and go into the "manual".  I also need to fix the manual so
> that it's versioned alongside PyBlosxom (i.e. we have a 1.1 manual that's
> separate from the 1.2 manual...).
> 

How are you writing the docs? Maybe it would be clever, if not so
already, if we had some generic doc-format here (Docbook, GuideXML [1],
LaTeX, whatever). So if someone wants to contribute some documentation
you get it in a specified format instead of mail, or doc (yuck) or
whatever (== less work for you to intergrate).

[1] http://www.gentoo.org/doc/en/xml-guide.xml (this is really nice)

> If anyone's playing in the code and wants to spruce up the doc-strings in
> the vicinity of where they're playing, that's always a big help.
> 
> 
> I think everyone who's working on stuff for 1.2 should send a quick status
> report.  I'll collate the reports into a "this is where we are" thing and
> post it on the web-site.  From that we can figure out how ambitious we
> want to be for 1.2 and go accordingly.
> 
> Can everyone try to send some kind of "this is what I'm working on and 
> this is where I'm at" report before Monday?
> 
> /will
> 

cheers & happy weekend
Steven


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click