python-markdown-discuss — A general purpose discussion list

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Ron G. <ro...@fl...>]

On Mar 23, 2009, at 3:27 PM, Yuri Takhteyev wrote:

>>> 1.  The wikilink behavior has changed in a non-backwards- 
>>> compatible way.
>>>  Before, [[WikiLink]] and [[wiki link]] were equivalent.  Now they  
>>> are not.
>>>  Personally, I preferred the old way.
>
> The new way is closer to what Wikipedia does, which is a big plus

Perhaps, but if that's the goal then actually doing it the way  
Wikipedia does it would be even better than just being "way closer."   
Wikipedia contracts multiple spaces down to one, but markdown.py  
doesn't.  Wikipedia allows wikilinks that start with an underscore;  
markdown.py doesn't.

In general, I think the wikilink canonicalization algorithm ought to  
have the property that two wikilinks that look like the "ought" to be  
the same actually are the same.  [[WikiLink]] and [[wiki link]] are  
perhaps arguable, but [[wiki link]] and [[wiki  link]] aren't IMO.

> I think. However, perhaps it would make sense to make this  
> configurable.

That would be fine with me.  Maybe this could even subsume base_url  
and end_url.

>
>> Well, the reason is that this (PHP) is an already existing and highly
>> distributed implementation. The idea is that one should be able to
>> pass the same source documents through any implementation and get  
>> back
>> the same result. So, I went with an already existing implementation.
>
> I agree with this completely. I think it would be great to have a set
> of extensions that get us as close as possible to PHP Markdown Extra.

That's a fine goal, but what's wrong with being a superset of PHP MD  
Extra?

rg

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Waylan L. <wa...@gm...>]

On Mon, Mar 23, 2009 at 4:21 PM, Ron Garret <ron...@gm...> wrote:
>
> On Mar 23, 2009, at 1:08 PM, Waylan Limberg wrote:
>
>> Thanks for the feedback Ron. I've responded you your concerns below to
>> keep things in context.
>>
>> On Mon, Mar 23, 2009 at 3:19 PM, Ron Garret <ron...@gm...>
>> wrote:
>>>
>>> 1.  The wikilink behavior has changed in a non-backwards-compatible
>>> way.
>>>  Before, [[WikiLink]] and [[wiki link]] were equivalent.  Now they
>>> are not.
>>>  Personally, I preferred the old way.
>>
>> What was the old way? I don't remember changing that. Could you
>> provide an example of the current output and the expected output?
>>
>
>
> The old one converted spaces to CamelCase.  The new one converts
> spaces to underscores.
>
Oh, sorry I misunderstood you. You put brackets around both. The old
way worked only on CamelCase and did not use brackets at all. The new
way only uses brackets and ignored case. If you notice, the extension
name even changed from "wikilink" to "wikilinks" (the "s" was added)
so that old code would not work without changes with the new
extension. The point is, this is actually a different extension.

As Yuri pointed out, this is actually considered a better wikilink
syntax. Of course, you are free to implement the old syntax if you
can. We ran into a few technical difficulties with some of the other
changes in the code, which is why we dropped the old. But we'd be be
happy to add it back in if you can get it to work.

-- 
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Yuri T. <qar...@gm...>]

>> 1.  The wikilink behavior has changed in a non-backwards-compatible way.
>>  Before, [[WikiLink]] and [[wiki link]] were equivalent.  Now they are not.
>>  Personally, I preferred the old way.

The new way is closer to what Wikipedia does, which is a big plus, I
think. However, perhaps it would make sense to make this configurable.
Right now we have

    label.replace(' ', '_')

in markdown/extensions/wikilinks.py

Both arguments to replace could perhaps be configurable, and the first
one should probably be treated as a regular expression. Alternatively,
we could have a config parameter that could be set to a function that
would be used to do the conversion, so you would have something like:

makeExtension(configs = {'make_url': lambda x: label.replace(' ', '')})

> Well, the reason is that this (PHP) is an already existing and highly
> distributed implementation. The idea is that one should be able to
> pass the same source documents through any implementation and get back
> the same result. So, I went with an already existing implementation.

I agree with this completely. I think it would be great to have a set
of extensions that get us as close as possible to PHP Markdown Extra.
People are free, however, to implement their own table extensions,
that have different behavior, and we can even add some of them to our
collections of extensions.

> Anyone is encouraged to branch and create their own extensions.

For extensions - definitely. Of course, it's good to always look for
opportunities for code reuse. E.g., instead of actually branching
code, it may be better to have a different extension that uses the
same module but just configures it differently.

- yuri

-- 
http://spu.tnik.org/

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Ron G. <ron...@gm...>]

On Mar 23, 2009, at 1:08 PM, Waylan Limberg wrote:

> Thanks for the feedback Ron. I've responded you your concerns below to
> keep things in context.
>
> On Mon, Mar 23, 2009 at 3:19 PM, Ron Garret <ron...@gm...>  
> wrote:
>> My pleasure.  Thanks for the code :-)
>>
>> Couple of comments.  These are really design issues, not bugs, but  
>> FWIW:
>>
>> 1.  The wikilink behavior has changed in a non-backwards-compatible  
>> way.
>>  Before, [[WikiLink]] and [[wiki link]] were equivalent.  Now they  
>> are not.
>>  Personally, I preferred the old way.
>
> What was the old way? I don't remember changing that. Could you
> provide an example of the current output and the expected output?
>


The old one converted spaces to CamelCase.  The new one converts  
spaces to underscores.


Old:

Python 2.6.1 (r261:67515, Dec  6 2008, 16:42:21)
[GCC 4.0.1 (Apple Computer, Inc. build 5370)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
 >>> import markdown
 >>> markdown.version
'1.7'
 >>> markdown.markdown('[[wiki link]]',['wikilink'])
u'<p><a href="/WikiLink/" class="wikilink">wiki link</a>\n</p>'


New:

 >>> import markdown
 >>> markdown.version
'2.0-rc1'
 >>> markdown.markdown('[[wiki link]]',['wikilinks'])
u'<p><a class="wikilink" href="/wiki_link/">wiki link</a></p>'
 >>>

rg

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Waylan L. <wa...@gm...>]

Thanks for the feedback Ron. I've responded you your concerns below to
keep things in context.

On Mon, Mar 23, 2009 at 3:19 PM, Ron Garret <ron...@gm...> wrote:
> My pleasure.  Thanks for the code :-)
>
> Couple of comments.  These are really design issues, not bugs, but FWIW:
>
> 1.  The wikilink behavior has changed in a non-backwards-compatible way.
>  Before, [[WikiLink]] and [[wiki link]] were equivalent.  Now they are not.
>  Personally, I preferred the old way.

What was the old way? I don't remember changing that. Could you
provide an example of the current output and the expected output?

> 2.  I don't like PHP table syntax because it makes it impossible to create a
> table without headers.  I know this has been discussed before (though have
> not been able to find that discussion -- can someone send me a pointer?) so
> maybe there's a sound reason for choosing this syntax over some of the
> alternatives, but at the moment I can't think what it might be.

Well, the reason is that this (PHP) is an already existing and highly
distributed implementation. The idea is that one should be able to
pass the same source documents through any implementation and get back
the same result. So, I went with an already existing implementation.

I was originally going to add in the option to allow tables without
headers, but that presented the problem of how to define column
alignment and I didn't want to introduce new syntax. On further
reflection, I realized that the purpose of a table (in Markdown even
more so than HTML) should only be for tabular data, and when does
tabular data not have column headers? I suppose it's possible, but
very unlikely. I suspect that is why the PHP implementation is so
restrictive in that regard.

Oh, you asked for a pointer to a previous discussion. Um, check the
markdown list [1]. There was a recent discussion regarding table
syntax with all sorts of alternatives discussed, but in the end, most
of it was more complex that what fits with the Markdown philosophy. So
I ignored those suggestions and went with what I believe to be the
mostly widely used existing implementation.

[1]: http://six.pairlist.net/pipermail/markdown-discuss/

> One good thing about the new code is that it's really easy for me to change
> these things myself.  :-)

And it is for that very reason that I left the syntax as-is. Anyone
can build upon the existing base - or even start over from scratch.

> I mention them only in case there's a desire to
> prevent people from branching too much.

Anyone is encouraged to branch and create their own extensions. That
is part of the point of our extension API. In fact, the extension API
is what we pride ourselves in most with the project - even before
performance. But, yeah, the default implementation isn't going to
branch to far from the existing standard for the reasons mentioned
above.

-- 
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Ron G. <ron...@gm...>]

My pleasure.  Thanks for the code :-)

Couple of comments.  These are really design issues, not bugs, but FWIW:

1.  The wikilink behavior has changed in a non-backwards-compatible  
way.  Before, [[WikiLink]] and [[wiki link]] were equivalent.  Now  
they are not.  Personally, I preferred the old way.

2.  I don't like PHP table syntax because it makes it impossible to  
create a table without headers.  I know this has been discussed before  
(though have not been able to find that discussion -- can someone send  
me a pointer?) so maybe there's a sound reason for choosing this  
syntax over some of the alternatives, but at the moment I can't think  
what it might be.

One good thing about the new code is that it's really easy for me to  
change these things myself.  :-)  I mention them only in case there's  
a desire to prevent people from branching too much.

rg


On Mar 23, 2009, at 12:00 PM, Waylan Limberg wrote:

> Hey Ron,
>
> I appreciate the testing. Especially considering that some of those
> changes were more than a simple bug-fix. I was intending to do another
> rc today (half-way between rc1 and when we plan on releasing 2.0
> final) but being out-of-town this past weekend, I haven't got to it
> yet.
>
> I also wanted to do another rc because I forgot to include a Python
> 3.0 version with the last rc as we had previously discussed. Hopefully
> I'll get these out tonight.
>
> On Mon, Mar 23, 2009 at 1:52 PM, Ron Garret <ron...@gm...>  
> wrote:
>> This is probably a stupid question, but since there have already been
>> changes since 2.0rc1 I want to check the code out directly from
>> gitorious.  How do I do it?  I know how to use git, I just don't know
>> which URI to use.
>>
>> Thanks,
>> rg
>>
>> On Mar 8, 2009, at 7:27 PM, Waylan Limberg wrote:
>>
>>> I am pleased to announce that after much hard work, a Release
>>> Candidate for Python Markdown version 2.0 is now available for
>>> [download][]. Please, download it, install it, test it, beat it...  
>>> and
>>> report any [bugs][]. Assuming no major bugs, we will release 2.0  
>>> final
>>> approximately one month from today. Until then, the project [site][]
>>> will continue to document version 1.7. Updated documentation is
>>> available in the `doc/` directory in the source files. Hopefully,  
>>> all
>>> the included extensions will be documented before the final release.
>>>
>>> [download]: https://sourceforge.net/project/showfiles.php?group_id=153041&package_id=183331&release_id=666767
>>> [bugs]: http://www.freewisdom.org/projects/python-markdown/Tickets
>>> [site]: http://www.freewisdom.org/projects/python-markdown
>>>
>>> Release Notes:
>>> ===========
>>>
>>> * Major refactor of the core and extension API. Extension authors
>>> should see the included documentation in
>>> `docs/writing_extensions.txt`. All parts of the syntax are now
>>> completely overridable by extensions.
>>>
>>> * Numerous extensions added to the standard distribution (off by
>>> default), including an "extra" extension which matches PHP Markdown
>>> Extra. See the `markdown/extensions/` directory for the full list.
>>>
>>> * The code has been refactored into a full Python library with a
>>> separate command line script.
>>>
>>> * Optional output of XHTML1 (default) or HTML4 with the option for
>>> extensions to add more.
>>>
>>> * Uses ElementTree to build (X)HTML document rather than home-grown
>>> NanoDom.
>>>
>>> * Most of the differences in Python-Markdown's output compared to  
>>> perl
>>> and/or php have been eliminated.
>>>
>>> * And much more... See the changelog and [Git log][] for more  
>>> details.
>>>
>>> [Git log]: http://gitorious.org/projects/python-markdown/repos/mainline/logs
>>>
>>> --
>>> ----
>>> \X/ /-\ `/ |_ /-\ |\|
>>> Waylan Limberg
>>>
>>> ------------------------------------------------------------------------------
>>> Open Source Business Conference (OSBC), March 24-25, 2009, San
>>> Francisco, CA
>>> -OSBC tackles the biggest issue in open source: Open Sourcing the
>>> Enterprise
>>> -Strategies to boost innovation and cut costs with open source
>>> participation
>>> -Receive a $600 discount off the registration fee with the source
>>> code: SFAD
>>> http://p.sf.net/sfu/XcvMzF8H
>>> _______________________________________________
>>> Python-markdown-discuss mailing list
>>> Pyt...@li...
>>> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>>
>>
>> ------------------------------------------------------------------------------
>> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM)  
>> are
>> powering Web 2.0 with engaging, cross-platform capabilities.  
>> Quickly and
>> easily build your RIAs with Flex Builder, the Eclipse(TM)based  
>> development
>> software that enables intelligent coding and step-through debugging.
>> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
>> _______________________________________________
>> Python-markdown-discuss mailing list
>> Pyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>>
>
>
>
> -- 
> ----
> \X/ /-\ `/ |_ /-\ |\|
> Waylan Limberg

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Waylan L. <wa...@gm...>]

Hey Ron,

I appreciate the testing. Especially considering that some of those
changes were more than a simple bug-fix. I was intending to do another
rc today (half-way between rc1 and when we plan on releasing 2.0
final) but being out-of-town this past weekend, I haven't got to it
yet.

I also wanted to do another rc because I forgot to include a Python
3.0 version with the last rc as we had previously discussed. Hopefully
I'll get these out tonight.

On Mon, Mar 23, 2009 at 1:52 PM, Ron Garret <ron...@gm...> wrote:
> This is probably a stupid question, but since there have already been
> changes since 2.0rc1 I want to check the code out directly from
> gitorious.  How do I do it?  I know how to use git, I just don't know
> which URI to use.
>
> Thanks,
> rg
>
> On Mar 8, 2009, at 7:27 PM, Waylan Limberg wrote:
>
>> I am pleased to announce that after much hard work, a Release
>> Candidate for Python Markdown version 2.0 is now available for
>> [download][]. Please, download it, install it, test it, beat it... and
>> report any [bugs][]. Assuming no major bugs, we will release 2.0 final
>> approximately one month from today. Until then, the project [site][]
>> will continue to document version 1.7. Updated documentation is
>> available in the `doc/` directory in the source files. Hopefully, all
>> the included extensions will be documented before the final release.
>>
>> [download]: https://sourceforge.net/project/showfiles.php?group_id=153041&package_id=183331&release_id=666767
>> [bugs]: http://www.freewisdom.org/projects/python-markdown/Tickets
>> [site]: http://www.freewisdom.org/projects/python-markdown
>>
>> Release Notes:
>> ===========
>>
>> * Major refactor of the core and extension API. Extension authors
>> should see the included documentation in
>> `docs/writing_extensions.txt`. All parts of the syntax are now
>> completely overridable by extensions.
>>
>> * Numerous extensions added to the standard distribution (off by
>> default), including an "extra" extension which matches PHP Markdown
>> Extra. See the `markdown/extensions/` directory for the full list.
>>
>> * The code has been refactored into a full Python library with a
>> separate command line script.
>>
>> * Optional output of XHTML1 (default) or HTML4 with the option for
>> extensions to add more.
>>
>> * Uses ElementTree to build (X)HTML document rather than home-grown
>> NanoDom.
>>
>> * Most of the differences in Python-Markdown's output compared to perl
>> and/or php have been eliminated.
>>
>> * And much more... See the changelog and [Git log][] for more details.
>>
>> [Git log]: http://gitorious.org/projects/python-markdown/repos/mainline/logs
>>
>> --
>> ----
>> \X/ /-\ `/ |_ /-\ |\|
>> Waylan Limberg
>>
>> ------------------------------------------------------------------------------
>> Open Source Business Conference (OSBC), March 24-25, 2009, San
>> Francisco, CA
>> -OSBC tackles the biggest issue in open source: Open Sourcing the
>> Enterprise
>> -Strategies to boost innovation and cut costs with open source
>> participation
>> -Receive a $600 discount off the registration fee with the source
>> code: SFAD
>> http://p.sf.net/sfu/XcvMzF8H
>> _______________________________________________
>> Python-markdown-discuss mailing list
>> Pyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



-- 
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Artem Y. <se...@sp...>]

On Mon, Mar 23, 2009 at 9:52 PM, Ron Garret <ron...@gm...> wrote:

> This is probably a stupid question, but since there have already been
> changes since 2.0rc1 I want to check the code out directly from
> gitorious.  How do I do it?  I know how to use git, I just don't know
> which URI to use.
>

You can clone current version with:
git clone git://gitorious.org/python-markdown/mainline.git


>
> Thanks,
> rg


Regards,
Artem


>
>
> On Mar 8, 2009, at 7:27 PM, Waylan Limberg wrote:
>
> > I am pleased to announce that after much hard work, a Release
> > Candidate for Python Markdown version 2.0 is now available for
> > [download][]. Please, download it, install it, test it, beat it... and
> > report any [bugs][]. Assuming no major bugs, we will release 2.0 final
> > approximately one month from today. Until then, the project [site][]
> > will continue to document version 1.7. Updated documentation is
> > available in the `doc/` directory in the source files. Hopefully, all
> > the included extensions will be documented before the final release.
> >
> > [download]:
> https://sourceforge.net/project/showfiles.php?group_id=153041&package_id=183331&release_id=666767
> > [bugs]: http://www.freewisdom.org/projects/python-markdown/Tickets
> > [site]: http://www.freewisdom.org/projects/python-markdown
> >
> > Release Notes:
> > ===========
> >
> > * Major refactor of the core and extension API. Extension authors
> > should see the included documentation in
> > `docs/writing_extensions.txt`. All parts of the syntax are now
> > completely overridable by extensions.
> >
> > * Numerous extensions added to the standard distribution (off by
> > default), including an "extra" extension which matches PHP Markdown
> > Extra. See the `markdown/extensions/` directory for the full list.
> >
> > * The code has been refactored into a full Python library with a
> > separate command line script.
> >
> > * Optional output of XHTML1 (default) or HTML4 with the option for
> > extensions to add more.
> >
> > * Uses ElementTree to build (X)HTML document rather than home-grown
> > NanoDom.
> >
> > * Most of the differences in Python-Markdown's output compared to perl
> > and/or php have been eliminated.
> >
> > * And much more... See the changelog and [Git log][] for more details.
> >
> > [Git log]:
> http://gitorious.org/projects/python-markdown/repos/mainline/logs
> >
> > --
> > ----
> > \X/ /-\ `/ |_ /-\ |\|
> > Waylan Limberg
> >
> >
> ------------------------------------------------------------------------------
> > Open Source Business Conference (OSBC), March 24-25, 2009, San
> > Francisco, CA
> > -OSBC tackles the biggest issue in open source: Open Sourcing the
> > Enterprise
> > -Strategies to boost innovation and cut costs with open source
> > participation
> > -Receive a $600 discount off the registration fee with the source
> > code: SFAD
> > http://p.sf.net/sfu/XcvMzF8H
> > _______________________________________________
> > Python-markdown-discuss mailing list
> > Pyt...@li...
> > https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>
>
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Ron G. <ron...@gm...>]

Thanks!

On Mar 23, 2009, at 11:26 AM, Yuri Takhteyev wrote:

> See http://gitorious.org/projects/python-markdown/repos/mainline
>
> - yuri
>
>
> On Mon, Mar 23, 2009 at 10:52 AM, Ron Garret <ron...@gm...>  
> wrote:
>> This is probably a stupid question, but since there have already been
>> changes since 2.0rc1 I want to check the code out directly from
>> gitorious.  How do I do it?  I know how to use git, I just don't know
>> which URI to use.
>>
>> Thanks,
>> rg
>>
>> On Mar 8, 2009, at 7:27 PM, Waylan Limberg wrote:
>>
>>> I am pleased to announce that after much hard work, a Release
>>> Candidate for Python Markdown version 2.0 is now available for
>>> [download][]. Please, download it, install it, test it, beat it...  
>>> and
>>> report any [bugs][]. Assuming no major bugs, we will release 2.0  
>>> final
>>> approximately one month from today. Until then, the project [site][]
>>> will continue to document version 1.7. Updated documentation is
>>> available in the `doc/` directory in the source files. Hopefully,  
>>> all
>>> the included extensions will be documented before the final release.
>>>
>>> [download]: https://sourceforge.net/project/showfiles.php?group_id=153041&package_id=183331&release_id=666767
>>> [bugs]: http://www.freewisdom.org/projects/python-markdown/Tickets
>>> [site]: http://www.freewisdom.org/projects/python-markdown
>>>
>>> Release Notes:
>>> ===========
>>>
>>> * Major refactor of the core and extension API. Extension authors
>>> should see the included documentation in
>>> `docs/writing_extensions.txt`. All parts of the syntax are now
>>> completely overridable by extensions.
>>>
>>> * Numerous extensions added to the standard distribution (off by
>>> default), including an "extra" extension which matches PHP Markdown
>>> Extra. See the `markdown/extensions/` directory for the full list.
>>>
>>> * The code has been refactored into a full Python library with a
>>> separate command line script.
>>>
>>> * Optional output of XHTML1 (default) or HTML4 with the option for
>>> extensions to add more.
>>>
>>> * Uses ElementTree to build (X)HTML document rather than home-grown
>>> NanoDom.
>>>
>>> * Most of the differences in Python-Markdown's output compared to  
>>> perl
>>> and/or php have been eliminated.
>>>
>>> * And much more... See the changelog and [Git log][] for more  
>>> details.
>>>
>>> [Git log]: http://gitorious.org/projects/python-markdown/repos/mainline/logs
>>>
>>> --
>>> ----
>>> \X/ /-\ `/ |_ /-\ |\|
>>> Waylan Limberg
>>>
>>> ------------------------------------------------------------------------------
>>> Open Source Business Conference (OSBC), March 24-25, 2009, San
>>> Francisco, CA
>>> -OSBC tackles the biggest issue in open source: Open Sourcing the
>>> Enterprise
>>> -Strategies to boost innovation and cut costs with open source
>>> participation
>>> -Receive a $600 discount off the registration fee with the source
>>> code: SFAD
>>> http://p.sf.net/sfu/XcvMzF8H
>>> _______________________________________________
>>> Python-markdown-discuss mailing list
>>> Pyt...@li...
>>> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>>
>>
>> ------------------------------------------------------------------------------
>> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM)  
>> are
>> powering Web 2.0 with engaging, cross-platform capabilities.  
>> Quickly and
>> easily build your RIAs with Flex Builder, the Eclipse(TM)based  
>> development
>> software that enables intelligent coding and step-through debugging.
>> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
>> _______________________________________________
>> Python-markdown-discuss mailing list
>> Pyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>>
>
>
>
> -- 
> http://spu.tnik.org/

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Yuri T. <qar...@gm...>]

See http://gitorious.org/projects/python-markdown/repos/mainline

 - yuri


On Mon, Mar 23, 2009 at 10:52 AM, Ron Garret <ron...@gm...> wrote:
> This is probably a stupid question, but since there have already been
> changes since 2.0rc1 I want to check the code out directly from
> gitorious.  How do I do it?  I know how to use git, I just don't know
> which URI to use.
>
> Thanks,
> rg
>
> On Mar 8, 2009, at 7:27 PM, Waylan Limberg wrote:
>
>> I am pleased to announce that after much hard work, a Release
>> Candidate for Python Markdown version 2.0 is now available for
>> [download][]. Please, download it, install it, test it, beat it... and
>> report any [bugs][]. Assuming no major bugs, we will release 2.0 final
>> approximately one month from today. Until then, the project [site][]
>> will continue to document version 1.7. Updated documentation is
>> available in the `doc/` directory in the source files. Hopefully, all
>> the included extensions will be documented before the final release.
>>
>> [download]: https://sourceforge.net/project/showfiles.php?group_id=153041&package_id=183331&release_id=666767
>> [bugs]: http://www.freewisdom.org/projects/python-markdown/Tickets
>> [site]: http://www.freewisdom.org/projects/python-markdown
>>
>> Release Notes:
>> ===========
>>
>> * Major refactor of the core and extension API. Extension authors
>> should see the included documentation in
>> `docs/writing_extensions.txt`. All parts of the syntax are now
>> completely overridable by extensions.
>>
>> * Numerous extensions added to the standard distribution (off by
>> default), including an "extra" extension which matches PHP Markdown
>> Extra. See the `markdown/extensions/` directory for the full list.
>>
>> * The code has been refactored into a full Python library with a
>> separate command line script.
>>
>> * Optional output of XHTML1 (default) or HTML4 with the option for
>> extensions to add more.
>>
>> * Uses ElementTree to build (X)HTML document rather than home-grown
>> NanoDom.
>>
>> * Most of the differences in Python-Markdown's output compared to perl
>> and/or php have been eliminated.
>>
>> * And much more... See the changelog and [Git log][] for more details.
>>
>> [Git log]: http://gitorious.org/projects/python-markdown/repos/mainline/logs
>>
>> --
>> ----
>> \X/ /-\ `/ |_ /-\ |\|
>> Waylan Limberg
>>
>> ------------------------------------------------------------------------------
>> Open Source Business Conference (OSBC), March 24-25, 2009, San
>> Francisco, CA
>> -OSBC tackles the biggest issue in open source: Open Sourcing the
>> Enterprise
>> -Strategies to boost innovation and cut costs with open source
>> participation
>> -Receive a $600 discount off the registration fee with the source
>> code: SFAD
>> http://p.sf.net/sfu/XcvMzF8H
>> _______________________________________________
>> Python-markdown-discuss mailing list
>> Pyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



-- 
http://spu.tnik.org/

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Ron G. <ron...@gm...>]

This is probably a stupid question, but since there have already been  
changes since 2.0rc1 I want to check the code out directly from  
gitorious.  How do I do it?  I know how to use git, I just don't know  
which URI to use.

Thanks,
rg

On Mar 8, 2009, at 7:27 PM, Waylan Limberg wrote:

> I am pleased to announce that after much hard work, a Release
> Candidate for Python Markdown version 2.0 is now available for
> [download][]. Please, download it, install it, test it, beat it... and
> report any [bugs][]. Assuming no major bugs, we will release 2.0 final
> approximately one month from today. Until then, the project [site][]
> will continue to document version 1.7. Updated documentation is
> available in the `doc/` directory in the source files. Hopefully, all
> the included extensions will be documented before the final release.
>
> [download]: https://sourceforge.net/project/showfiles.php?group_id=153041&package_id=183331&release_id=666767
> [bugs]: http://www.freewisdom.org/projects/python-markdown/Tickets
> [site]: http://www.freewisdom.org/projects/python-markdown
>
> Release Notes:
> ===========
>
> * Major refactor of the core and extension API. Extension authors
> should see the included documentation in
> `docs/writing_extensions.txt`. All parts of the syntax are now
> completely overridable by extensions.
>
> * Numerous extensions added to the standard distribution (off by
> default), including an "extra" extension which matches PHP Markdown
> Extra. See the `markdown/extensions/` directory for the full list.
>
> * The code has been refactored into a full Python library with a
> separate command line script.
>
> * Optional output of XHTML1 (default) or HTML4 with the option for
> extensions to add more.
>
> * Uses ElementTree to build (X)HTML document rather than home-grown  
> NanoDom.
>
> * Most of the differences in Python-Markdown's output compared to perl
> and/or php have been eliminated.
>
> * And much more... See the changelog and [Git log][] for more details.
>
> [Git log]: http://gitorious.org/projects/python-markdown/repos/mainline/logs
>
> -- 
> ----
> \X/ /-\ `/ |_ /-\ |\|
> Waylan Limberg
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San  
> Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the  
> Enterprise
> -Strategies to boost innovation and cut costs with open source  
> participation
> -Receive a $600 discount off the registration fee with the source  
> code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss

Re: [Python-markdown-discuss] And another bug report: concerning TOC

[Holger R. <Hol...@gm...>]

Hi,

>>
>> I only discovered one bug. I wanted to add a <hr> after my toc, so i
>> did:
>>
>> <snip>
>> [TOC]
>> ----------
>> </snap>
>
> Well, without the toc extension, that produces ``<h2>[TOC]</h2>`` [1].
> So don't do that. You wouldn't get a ``<hr>`` anyway. If you really
> want a ``<hr>``, you need to have a blank line before it.
Aah, this was entirely my fault. I keep forgetting about marking  
headlines
this way.

> That said, it shouldn't crash. So I just pushed a fix and test. Thanks
> for the report.
Agreed. Thanks for fixing! Thanks for the quick reply!

Cheers,
Holger

Re: [Python-markdown-discuss] And another bug report: concerning TOC

[Waylan L. <wa...@gm...>]

On Wed, Mar 18, 2009 at 5:07 PM, Holger Rapp <Hol...@gm...> wrote:
> Hey,
>
> i just found the TOC extension in current git repository, and I love it!

Glad to hear it.

>
> I only discovered one bug. I wanted to add a <hr> after my toc, so i
> did:
>
> <snip>
> [TOC]
> ----------
> </snap>

Well, without the toc extension, that produces ``<h2>[TOC]</h2>`` [1].
So don't do that. You wouldn't get a ``<hr>`` anyway. If you really
want a ``<hr>``, you need to have a blank line before it.

That said, it shouldn't crash. So I just pushed a fix and test. Thanks
for the report.

It turns out the marker was causing an infinite loop where it would
build a new toc inside the toc item pointing to the header with the
marker. To avoid it, I have disallowed the marker in any headers
(h1-6). The marker is just passed through as text in the header
(``<h2>[TOC]</h2>``). The unexpected result should clue the document
author into the problem with his/her markup without any crashes.

[1]: http://babelmark.bobtfish.net/?markdown=[TOC]%0D%0A----------


-- 
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg

[Python-markdown-discuss] And another bug report: concerning TOC

[Holger R. <Hol...@gm...>]

Hey,

i just found the TOC extension in current git repository, and I love it!

I only discovered one bug. I wanted to add a <hr> after my toc, so i  
did:

<snip>
[TOC]
----------
</snap>

this crashes my interpretor. Here is a snippet to reproduce.

$ m = markdown.Markdown(("toc",)); m.convert("[TOC]\n-------")

current git revision.

Greetings,
Holger

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Artem Y. <se...@sp...>]

On Tue, Mar 17, 2009 at 6:05 PM, Waylan Limberg <wa...@gm...> wrote:

> Thanks Artem. Are those numbers averages from multiple runs there? In
> other words, is this something I can use in the release notes?
> Although, all I really need is a percentage of change - probably just
> for the "markdown-syntax" document.


I got this numbers using test-markdown.py, it repeats every test 10 times,
so it's not average, it's sum, but for percentage it will be enough. I did
it few times and numbers were almost the same.
But I can redo it with timeit module to get better accuracy.


>
>
> On Fri, Mar 13, 2009 at 5:38 PM, Artem Yunusov <se...@sp...> wrote:
> > On Wed, Mar 11, 2009 at 4:17 AM, Yuri Takhteyev <qar...@gm...>
> wrote:
> >> BTW, has anyone done any benchmarks recently comparing the performance
> >> of this new release candidate to 1.7?
> >
> > I did today, here is some of the results:
> >
> > 1.7 version:
> > markdown-syntax:1.240000
> > bracket_re:2.870000
> > ordered-and-unordered-list:0.190000
> >
> > 2.0 release candidate:
> > markdown-syntax:0.880000
> > bracket_re:1.670000
> > ordered-and-unordered-list:0.150000
>
>
>
>
> --
> ----
> \X/ /-\ `/ |_ /-\ |\|
> Waylan Limberg


Regards,
Artem

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Waylan L. <wa...@gm...>]

Thanks Artem. Are those numbers averages from multiple runs there? In
other words, is this something I can use in the release notes?
Although, all I really need is a percentage of change - probably just
for the "markdown-syntax" document.

On Fri, Mar 13, 2009 at 5:38 PM, Artem Yunusov <se...@sp...> wrote:
> On Wed, Mar 11, 2009 at 4:17 AM, Yuri Takhteyev <qar...@gm...> wrote:
>> BTW, has anyone done any benchmarks recently comparing the performance
>> of this new release candidate to 1.7?
>
> I did today, here is some of the results:
>
> 1.7 version:
> markdown-syntax:1.240000
> bracket_re:2.870000
> ordered-and-unordered-list:0.190000
>
> 2.0 release candidate:
> markdown-syntax:0.880000
> bracket_re:1.670000
> ordered-and-unordered-list:0.150000




-- 
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg

Re: [Python-markdown-discuss] Command line script & Windows

[Yuri T. <qar...@gm...>]

> that they get around this by spelling the command line script
> differently - usually with capitalization. In most cases the lib is
> CamelCased and the script is all lower case. Obviously, to retain
> backwards compatibility that's not an option for us.

We shouldn't rename the library name, but we _can_ give a different
name to the executable on Windows.

 - yuri

-- 
http://spu.tnik.org/

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Artem Y. <se...@sp...>]

On Wed, Mar 11, 2009 at 4:17 AM, Yuri Takhteyev <qar...@gm...> wrote:

> > Glad it's almost released! I think performance increase should be also
> > mentioned.
>
> Yes, as well as the fact that Artem's work was crucial for getting
> this version of the ground last summer!
>

Thanks,


>
> BTW, has anyone done any benchmarks recently comparing the performance
> of this new release candidate to 1.7?
>

I did today, here is some of the results:

1.7 version:
markdown-syntax:1.240000
bracket_re:2.870000
ordered-and-unordered-list:0.190000

2.0 release candidate:
markdown-syntax:0.880000
bracket_re:1.670000
ordered-and-unordered-list:0.150000

So it didn't lose speed superiority!


> - yuri
>

Regards,
Artem


>
> --
> http://spu.tnik.org/
>

[Python-markdown-discuss] Command line script & Windows

[Waylan L. <wa...@gm...>]

So I finally got around to testing the exe installable for 2.0-rc1
today. It worked fine, but the command line script does not work
properly. It seems that on Windows, when a command line script tries
to import a lib of the same name it fails. Apparently, it tries to
import itself instead and returns an import error. AFAICT, this is
*not* a problem in Linux systems.

Looking at a few other libs I have installed on my system, it appears
that they get around this by spelling the command line script
differently - usually with capitalization. In most cases the lib is
CamelCased and the script is all lower case. Obviously, to retain
backwards compatibility that's not an option for us.

Anyone have any suggestions or know of any solutions?
-- 
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg

Re: [Python-markdown-discuss] Bug report concerning tables

[Waylan L. <wa...@gm...>]

FYI, I just pushed this to the Git repo. Check it out and report back
with any problems.

As an aside, I am really loving the improvements we made to the
extension API. I didn't spend more than 2 hours total (including
researching existing syntax etc) to do everything. And most of one of
those hours was wasted fretting over the html4 vs. xhtml output. I
think it's possible to do anything with an extension now.

On Tue, Mar 10, 2009 at 4:50 PM, Waylan Limberg <wa...@gm...> wrote:
> Btw, before you spend your time working on this, I just whipped one
> up. I still have a few edge cases to work out, but I think I'll be
> replacing the existing tables extension once I do.
>
> One thing that almost had me stumped is ElementTree's output for empty
> cells. I'm getting ``<td />`` rather than ``<td></td>``. If I give all
> empty cells a single space, then I get ``<td> </td>``, but that feels
> like a dirty hack and doesn't match PHP's output either. If I switch
> ``output_format='HTML4'``, then I get the desired ``<td></td>``. As it
> turns out, the XHTML output (``<td />``) is valid XHTML (I just
> checked), so I guess I'll leave it.
>
> On Tue, Mar 10, 2009 at 8:48 AM, Waylan Limberg <wa...@gm...> wrote:
>> Your welcome Holger. See `docs/writing_extensions.txt` in the source
>> for full documentation. You may also want to look at the definition
>> list extension as an example.
>>
>> On Tue, Mar 10, 2009 at 3:54 AM, Holger Rapp <Ra...@mr...> wrote:
>>> Thanks for the quick fix, waylan. I will check it out, most probably
>>> this weekend.
>>> Can you point me to examples/documentation for implementing a
>>> blockprocessor extension? I badly need table support
>>> for the wiki of widelands.org and I will most likely hack something
>>> anyway, so I can as well do it right and implement it in markdown.
>>>
>>> Greetings,
>>> Holger
>>>
>>>
>>> Am 10.03.2009 um 03:49 schrieb Waylan Limberg:
>>>
>>>> On Mon, Mar 9, 2009 at 4:49 AM, Holger Rapp <Ra...@mr...> wrote:
>>>> [snip]
>>>>>
>>>>> tables extension seems to replace all <p> elements with <table>...
>>>>> This is
>>>>> pretty broken.
>>>>>
>>>>
>>>> Thanks for the report Holger. I just pushed a fix to the repo. Turns
>>>> out that code was pretty naive. This is the first I've looked at that
>>>> extension very closely and I'd say the entire extension could use a
>>>> refactor (rewritten as a blockprocessor), but at least a fix is in for
>>>> now.
>>>>
>>>> --
>>>> ----
>>>> \X/ /-\ `/ |_ /-\ |\|
>>>> Waylan Limberg
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Python-markdown-discuss mailing list
>>> Pyt...@li...
>>> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>>>
>>
>>
>>
>> --
>> ----
>> \X/ /-\ `/ |_ /-\ |\|
>> Waylan Limberg
>>
>
>
>
> --
> ----
> \X/ /-\ `/ |_ /-\ |\|
> Waylan Limberg
>



-- 
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Yuri T. <qar...@gm...>]

> Glad it's almost released! I think performance increase should be also
> mentioned.

Yes, as well as the fact that Artem's work was crucial for getting
this version of the ground last summer!

BTW, has anyone done any benchmarks recently comparing the performance
of this new release candidate to 1.7?

- yuri

-- 
http://spu.tnik.org/

Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Artem Y. <se...@sp...>]

Glad it's almost released! I think performance increase should be also
mentioned.

Best Regards,
Artem Yunusov

On Mon, Mar 9, 2009 at 6:27 AM, Waylan Limberg <wa...@gm...> wrote:

> I am pleased to announce that after much hard work, a Release
> Candidate for Python Markdown version 2.0 is now available for
> [download][]. Please, download it, install it, test it, beat it... and
> report any [bugs][]. Assuming no major bugs, we will release 2.0 final
> approximately one month from today. Until then, the project [site][]
> will continue to document version 1.7. Updated documentation is
> available in the `doc/` directory in the source files. Hopefully, all
> the included extensions will be documented before the final release.
>
> [download]:
> https://sourceforge.net/project/showfiles.php?group_id=153041&package_id=183331&release_id=666767
> [bugs]: http://www.freewisdom.org/projects/python-markdown/Tickets
> [site]: http://www.freewisdom.org/projects/python-markdown
>
> Release Notes:
> ===========
>
> * Major refactor of the core and extension API. Extension authors
> should see the included documentation in
> `docs/writing_extensions.txt`. All parts of the syntax are now
> completely overridable by extensions.
>
> * Numerous extensions added to the standard distribution (off by
> default), including an "extra" extension which matches PHP Markdown
> Extra. See the `markdown/extensions/` directory for the full list.
>
> * The code has been refactored into a full Python library with a
> separate command line script.
>
> * Optional output of XHTML1 (default) or HTML4 with the option for
> extensions to add more.
>
> * Uses ElementTree to build (X)HTML document rather than home-grown
> NanoDom.
>
> * Most of the differences in Python-Markdown's output compared to perl
> and/or php have been eliminated.
>
> * And much more... See the changelog and [Git log][] for more details.
>
> [Git log]:
> http://gitorious.org/projects/python-markdown/repos/mainline/logs
>
> --
> ----
> \X/ /-\ `/ |_ /-\ |\|
> Waylan Limberg
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
> CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the
> Enterprise
> -Strategies to boost innovation and cut costs with open source
> participation
> -Receive a $600 discount off the registration fee with the source code:
> SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>

Re: [Python-markdown-discuss] Bug report concerning tables

[Waylan L. <wa...@gm...>]

Btw, before you spend your time working on this, I just whipped one
up. I still have a few edge cases to work out, but I think I'll be
replacing the existing tables extension once I do.

One thing that almost had me stumped is ElementTree's output for empty
cells. I'm getting ``<td />`` rather than ``<td></td>``. If I give all
empty cells a single space, then I get ``<td> </td>``, but that feels
like a dirty hack and doesn't match PHP's output either. If I switch
``output_format='HTML4'``, then I get the desired ``<td></td>``. As it
turns out, the XHTML output (``<td />``) is valid XHTML (I just
checked), so I guess I'll leave it.

On Tue, Mar 10, 2009 at 8:48 AM, Waylan Limberg <wa...@gm...> wrote:
> Your welcome Holger. See `docs/writing_extensions.txt` in the source
> for full documentation. You may also want to look at the definition
> list extension as an example.
>
> On Tue, Mar 10, 2009 at 3:54 AM, Holger Rapp <Ra...@mr...> wrote:
>> Thanks for the quick fix, waylan. I will check it out, most probably
>> this weekend.
>> Can you point me to examples/documentation for implementing a
>> blockprocessor extension? I badly need table support
>> for the wiki of widelands.org and I will most likely hack something
>> anyway, so I can as well do it right and implement it in markdown.
>>
>> Greetings,
>> Holger
>>
>>
>> Am 10.03.2009 um 03:49 schrieb Waylan Limberg:
>>
>>> On Mon, Mar 9, 2009 at 4:49 AM, Holger Rapp <Ra...@mr...> wrote:
>>> [snip]
>>>>
>>>> tables extension seems to replace all <p> elements with <table>...
>>>> This is
>>>> pretty broken.
>>>>
>>>
>>> Thanks for the report Holger. I just pushed a fix to the repo. Turns
>>> out that code was pretty naive. This is the first I've looked at that
>>> extension very closely and I'd say the entire extension could use a
>>> refactor (rewritten as a blockprocessor), but at least a fix is in for
>>> now.
>>>
>>> --
>>> ----
>>> \X/ /-\ `/ |_ /-\ |\|
>>> Waylan Limberg
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Python-markdown-discuss mailing list
>> Pyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>>
>
>
>
> --
> ----
> \X/ /-\ `/ |_ /-\ |\|
> Waylan Limberg
>



-- 
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg

Re: [Python-markdown-discuss] Bug report concerning tables

[Waylan L. <wa...@gm...>]

Your welcome Holger. See `docs/writing_extensions.txt` in the source
for full documentation. You may also want to look at the definition
list extension as an example.

On Tue, Mar 10, 2009 at 3:54 AM, Holger Rapp <Ra...@mr...> wrote:
> Thanks for the quick fix, waylan. I will check it out, most probably
> this weekend.
> Can you point me to examples/documentation for implementing a
> blockprocessor extension? I badly need table support
> for the wiki of widelands.org and I will most likely hack something
> anyway, so I can as well do it right and implement it in markdown.
>
> Greetings,
> Holger
>
>
> Am 10.03.2009 um 03:49 schrieb Waylan Limberg:
>
>> On Mon, Mar 9, 2009 at 4:49 AM, Holger Rapp <Ra...@mr...> wrote:
>> [snip]
>>>
>>> tables extension seems to replace all <p> elements with <table>...
>>> This is
>>> pretty broken.
>>>
>>
>> Thanks for the report Holger. I just pushed a fix to the repo. Turns
>> out that code was pretty naive. This is the first I've looked at that
>> extension very closely and I'd say the entire extension could use a
>> refactor (rewritten as a blockprocessor), but at least a fix is in for
>> now.
>>
>> --
>> ----
>> \X/ /-\ `/ |_ /-\ |\|
>> Waylan Limberg
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



-- 
----
\X/ /-\ `/ |_ /-\ |\|
Waylan Limberg

Re: [Python-markdown-discuss] Bug report concerning tables

[Holger R. <Ra...@mr...>]

Thanks for the quick fix, waylan. I will check it out, most probably  
this weekend.
Can you point me to examples/documentation for implementing a  
blockprocessor extension? I badly need table support
for the wiki of widelands.org and I will most likely hack something  
anyway, so I can as well do it right and implement it in markdown.

Greetings,
Holger


Am 10.03.2009 um 03:49 schrieb Waylan Limberg:

> On Mon, Mar 9, 2009 at 4:49 AM, Holger Rapp <Ra...@mr...> wrote:
> [snip]
>>
>> tables extension seems to replace all <p> elements with <table>...  
>> This is
>> pretty broken.
>>
>
> Thanks for the report Holger. I just pushed a fix to the repo. Turns
> out that code was pretty naive. This is the first I've looked at that
> extension very closely and I'd say the entire extension could use a
> refactor (rewritten as a blockprocessor), but at least a fix is in for
> now.
>
> -- 
> ----
> \X/ /-\ `/ |_ /-\ |\|
> Waylan Limberg