Re: [Python-markdown-discuss] cleaning up the code

[Erick T. <ida...@us...>]

With the whole text preprocessor, I can use re.finditer to find all the 
matches in a string, instead of having to test a regex against each line 
and maintain state between lines, so it can be a little easier to use. I 
haven't done too many performance tests, but on a large string, it ought 
to be faster since the string searching should remain in the c kernel.

-e


Yuri Takhteyev wrote:
> Thanks for this patch.  About the preprocessors: did you actually get
> a noticeable performance improvement with this?  If so, I will be
> happy to put it in.
>
>  - yuri
>
> On 5/15/07, Erick Tryzelaar <ida...@us...> wrote:
>> I noticed that the code for markdown.py isn't consistent in how it does
>> spaces. I've tried to normalize it to the python coding standard, 
>> from here:
>>
>> http://www.python.org/dev/peps/pep-0008/
>>
>> I've also made the objects subclass from object, if that's alright. This
>> also assumes that my previous patch has been applied, so if you don't
>> want the text preprocessors, we'll have to edit this patch.
>>
>> I uploaded the patch here, since it's kind of big:
>>
>> http://sourceforge.net/tracker/index.php?func=detail&aid=1719072&group_id=153041&atid=790200 
>>
>>
>> -e
>>
>> ------------------------------------------------------------------------- 
>>
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> Python-markdown-discuss mailing list
>> Pyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>>
>
>