Re: [Python-markdown-discuss] GSoC version merged to mainline

[Artem Y. <ne...@gm...>]

Waylan Limberg wrote:
> On Wed, Aug 6, 2008 at 10:34 PM, Waylan Limberg <wa...@gm...> wrote:
>   
>> On Wed, Aug 6, 2008 at 6:41 PM, Artem Yunusov <ne...@gm...> wrote:
>>     
>>> Yep, I'll update doc strings by myself. Thanks for the link to PEP 257.
>>> I think extension writers need to know about markdown.etree module
>>> object, and also, that all data in <inline> tag will be processed by
>>> inline patterns, other functions, like indentETree is useless for them.
>>> I think we should write about all this on site in "Writing Extensions"
>>> section.
>>>       
>> I agree. Actually, that section needs to be completely reworked as a
>> number of additions/changes have happened to the extension API since
>> that page was last updated. The thing is, we don't want to update that
>> page until after 2.0 final is released or people may expect it to
>> apply to 1.7. I think maybe we should throw a text file in git for now
>> and copy it over the the wiki when we release. If you write up the
>> docs for the stuff you did Artem, I'll do the rest - unless you beat
>> me to it..
>>     
>
> FYI, I just committed a rough draft. Artem, I left the section on DOM
> manipulation for you. Any criticisms, suggestions or corrections are
> welcome. I'll copy it to the wiki when we release 2.0 final.
>   

Thanks, I'll write about it. One suggestion, I think we should not call 
ElementTree object - DOM, because it's slightly different things, as far 
as understand.