I finally got around to merging a bunch of patches and fixing all of
the open tickets except for one, so this makes the 1.6b release
candidate. Instead of posting it on the website immediately, I
decided to check it into SVN, in case someone finds any bugs.
I am also making one small change that the first thing towards what I
see as the new focus for 1.7: Right now the "standard" way to use
markdown is to call markdown.markdown(text) which really just makes a
call to markdown.Markdown(text).toString(). I am changing the latter
to markdown.Markdown().convert(text) to make it clear that you can
reuse the same instance of markdown to convert multiple text strings.
I am guessing that if used properly with something like Django this
can save CPU and perhaps memory. More generally, I want to think more
about performance rather than features for 1.7., especially in case of
web use with mod_python or FastCGI where a single instance can be used
over time. If anyone has time to spare and wants to help out with
such performance tuning, please let me know.
- yuri
--
Yuri Takhteyev
UC Berkeley School of Information
http://www.freewisdom.org/
|
