python-markdown-discuss — A general purpose discussion list

[Python-markdown-discuss] Shipping mathjax extension by default?

[Dmitry S. <mi...@gm...>]

Hi Waylan (and everybody subscribed)!

There's a [wonderful extension][1] at GitHub that adds support for
math formulas using [MathJax][2]. I've been using it myself for a
while and added support for it to my [ReText editor][3] (will be
available in 4.0 release).

It's very small (less than 20 lines of code) and does its job well.

Will it be possible to ship it by default in python-markdown? I can
prepare a pull request if needed.

[1]: https://github.com/mayoff/python-markdown-mathjax
[2]: http://www.mathjax.org/
[3]: http://retext.sourceforge.net/

Cheers,

--
Dmitry Shachnev

Re: [Python-markdown-discuss] How do I get the raw text from a file?

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

You might what to check out https://github.com/mrcoles/readmd

Not sure it it will do what you want. Another option would be to run
your text through markdown, then run markdown's output through a HTML
parser. Then use the parse tree's "return text only feature" to get
raw text with no markup. I'd start with either the html5lib [1] or
lxml [2] html parsers. I prefer lxml, but it is a C lib and not so
easy to install. But once you get it working, it is worth the effort.

[1]: https://code.google.com/p/html5lib/
[2]: http://lxml.de/

Hope that helps.

Waylan

On Thu, May 31, 2012 at 5:59 PM, Mandaris <man...@gm...> wrote:
> I'm new to python and I'm trying to make a script that will strip out the
> meta data and give me the raw text.
>
> --
> Valediction,
> Mandaris Moore III
> (916) 538 - 2611
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



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

[Python-markdown-discuss] How do I get the raw text from a file?

[Mandaris <man...@gm...>]

I'm new to python and I'm trying to make a script that will strip out the
meta data and give me the raw text.

-- 
Valediction,
Mandaris Moore III
(916) 538 - 2611

[Python-markdown-discuss] Version 2.2.0.Alpha Released

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

I just released version 2.2.0.Alpha of Python-Markdown.

Get it here: https://github.com/waylan/Python-Markdown/downloads

Read the release notes:
https://github.com/waylan/Python-Markdown/blob/master/docs/release-2.2.0.txt

Test it and report bugs: https://github.com/waylan/Python-Markdown/issues

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

Re: [Python-markdown-discuss] extensions for python markdown

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

On Sat, Apr 21, 2012 at 5:59 PM, AL <new...@al...> wrote:
> I'd like to announce the release of a couple of extensions we've been
> working on since last year.

Thanks Alex. I've just added them to the [wiki
page](https://github.com/waylan/Python-Markdown/wiki/Third-Party-Extensions).

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

[Python-markdown-discuss] extensions for python markdown

[AL <new...@al...>]

Hi,

I'd like to announce the release of a couple of extensions we've been 
working on since last year. I finally took time to release them today. 
They were developed in the context of [Active 
Archives](http://activearchives.org/), a research project about the 
practice of archiving in cultural institutions. Maybe they can benefit 
to the community...

mdx_cite
--------
An extension to support the <cite> tag

- <http://git.constantvzw.org/?p=aa.mdx_cite.git;a=tree>
- <https://github.com/aleray/mdx_cite>
- <http://pypi.python.org/pypi/mdx_cite/1.0>

     >>> import markdown
     >>> src = '"""Who Is Killing the Great Chefs of Europe?""" is the 
last movie I watched.'
     >>> html = markdown.markdown(src, ['cite'])
     >>> print(html)
     <p><cite>Who Is Killing the Great Chefs of Europe?</cite> is the 
last movie I watched.</p>

mdx_del_ins
-----------

An extension to support the <del> and <ins> tags

- <http://git.constantvzw.org/?p=aa.mdx_del_ins.git;a=tree>
- <https://github.com/aleray/mdx_del_ins>
- <http://pypi.python.org/pypi/mdx_del_ins/1.0>

     >>> import markdown
     >>> src = """This is ++added content++ and this is ~~deleted 
content~~"""
     >>> html = markdown.markdown(src, ['del_ins'])
     >>> print(html)
     <p>This is <ins>added content</ins> and this is <del>deleted 
content</del>
     </p>

mdx_outline
-----------

An extension to wrap the document logical sections (as implied by h1-h6 
headings)

- <http://git.constantvzw.org/?p=aa.mdx_outline.git;a=tree>
- <https://github.com/aleray/mdx_outline>
- <http://pypi.python.org/pypi/mdx_outline/1.0>

This is a rewrite of the mdx_addsection extension we've written for 
active archives. The first version had a bug with non hierachical 
heading structures. This is no longer a problem: a couple of weeks ago, 
Jesse Dhillon pushed to github a similar plugin which fixes the problem. 
Thanks to him, mdx_outline no longer has the problem.

     >>> import markdown
     >>> src = """
     ... # 1
     ... Section 1
     ... ## 1.1
     ... Subsection 1.1
     ... ## 1.2
     ... Subsection 1.2
     ... ### 1.2.1
     ... Hey 1.2.1 Special section
     ... ### 1.2.2
     ... #### 1.2.2.1
     ... # 2
     ... Section 2
     ... """.strip()
     >>> html = markdown.markdown(src, ['sections'])
     >>> print(html)
     <section class="section1"><h1>1</h1>
     <p>Section 1</p>
     <section class="section2"><h2>1.1</h2>
     <p>Subsection 1.1</p>
     </section><section class="section2"><h2>1.2</h2>
     <p>Subsection 1.2</p>
     <section class="section3"><h3>1.2.1</h3>
     <p>Hey 1.2.1 Special section</p>
     </section><section class="section3"><h3>1.2.2</h3>
     <section class="section4"><h4>1.2.2.1</h4>
     </section></section></section></section><section 
class="section1"><h1>2</h1>
     <p>Section 2</p>
     </section>

mdx_semanticdata
----------------

An extension to add support for semantic data (RDFa).

- <http://git.constantvzw.org/?p=aa.mdx_semanticdata.git;a=tree>
- <https://github.com/aleray/mdx_semanticdata>
- <http://pypi.python.org/pypi/mdx_semanticdata/1.0>

     >>> import markdown
     >>> text = "%%dc:author :: Sherry Turkle | Turkle's%% 
%%dc:title::Second Self%% was an early book on the social aspects of 
computation."
     >>> html = markdown.markdown(text, ['semanticdata'])
     >>> print(html)
     <p><span content="Sherry Turkle" 
property="dc:author">Turkle's</span> <span content="Second Self" 
property="dc:title">Second Self</span> was an early book on the social 
aspects of computation.</p>

mdx_semanticwikilinks
---------------------

An extension to add support for semantic (wiki)links (RDFa).

- <http://git.constantvzw.org/?p=aa.mdx_semanticwikilinks.git;a=tree>
- <https://github.com/aleray/mdx_semanticwikilinks>
- <http://pypi.python.org/pypi/mdx_semanticwikilinks/1.0>

     >>> md = markdown.Markdown(extensions=['semanticwikilinks'],
     ...         extension_configs={'semanticwikilinks' : [('namespace', 
'mynamespace')]})
     >>> html = md.convert('[[ Speaker :: Sherry Turkle | Second Self ]]')
     >>> print(html)
     <p><a href="Sherry Turkle" rel="mynamespace:Speaker">Second 
Self</a></p>


All the best,

-- Alex

Re: [Python-markdown-discuss] Confused about enable_attributes behavior

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

That sounds like a bug. Feel free to file a ticket here:

https://github.com/waylan/Python-Markdown/issues

On Thu, Mar 22, 2012 at 11:50 AM, Edward S. Vinyard
<ed....@gm...> wrote:
> I'm a new python-markdown user, so my apologies if this question has
> an obvious answer.
>
> Per the library reference's advice regarding safe_mode, I want to
> disable attributes.  When I use enable_attributes=False, however, the
> first occurrence of a boldfaced or italicized word/phrase truncates
> the output until the next paragraph break or heading.  E.g.:
>
>     Python 2.6.5 (r265:79063, Apr 16 2010, 13:09:56)
>     [GCC 4.4.3] on linux2
>     Type "help", "copyright", "credits" or "license" for more information.
>     >>> import markdown
>    >>> markdown.version
>    '2.1.1'
>    >>> markdown.markdown(' a *test* ', enable_attributes=True)
>    u'<p>a <em>test</em> </p>'
>    >>> markdown.markdown(' a *test* ', enable_attributes=False)
>    u'<p>a </p>'
>
> My expectation was that enable_attributes=False wouldn't change this
> behavior.  Am I way off?
>
> Thanks in advance,
> Ed
>
> P.S.: See treeprocessors.py starting at line 307.
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss



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

[Python-markdown-discuss] Confused about enable_attributes behavior

[Edward S. V. <ed....@gm...>]

I'm a new python-markdown user, so my apologies if this question has
an obvious answer.

Per the library reference's advice regarding safe_mode, I want to
disable attributes.  When I use enable_attributes=False, however, the
first occurrence of a boldfaced or italicized word/phrase truncates
the output until the next paragraph break or heading.  E.g.:

    Python 2.6.5 (r265:79063, Apr 16 2010, 13:09:56)
    [GCC 4.4.3] on linux2
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import markdown
    >>> markdown.version
    '2.1.1'
    >>> markdown.markdown(' a *test* ', enable_attributes=True)
    u'<p>a <em>test</em> </p>'
    >>> markdown.markdown(' a *test* ', enable_attributes=False)
    u'<p>a </p>'

My expectation was that enable_attributes=False wouldn't change this
behavior.  Am I way off?

Thanks in advance,
Ed

P.S.: See treeprocessors.py starting at line 307.

[Python-markdown-discuss] Python-Markdown 2.1.1 Released

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

Python Markdown version 2.1.1 has been released.

This is a bug fix release which fixes a few bugs which caused the
parser to choke on certain edge cases.

Everyone is encouraged to upgrade.

http://pypi.python.org/pypi/Markdown/2.1.1

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

Re: [Python-markdown-discuss] HTML Encoding Issues within Output of Custom Extension

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

On Wed, Jan 18, 2012 at 2:28 PM, andrew thornton
<ath...@gm...> wrote:
> On Wed, Jan 18, 2012 at 2:03 PM, Waylan Limberg <wa...@gm...> wrote:
>> On Wed, Jan 18, 2012 at 1:12 PM, andrew thornton
>> <ath...@gm...> wrote:
>>>
>>> Thank you for your reply,
>>>
>>> I have been trying to use htmlStash within the Galleria class, but
>>> this isn't working. I have however been able to use ET to return the
>>> errors. Here is what I was trying:
>>>
>>> class Galleria(markdown.inlinepatterns.Pattern):
>>>    def handleMatch(self, m):
>>>        try:
>>>            images =
>>> SuperPage.objects.get(id=m.group('superpage_id')).superpageimage_set.all()
>>>        except:
>>>            images = None
>>>        if images:
>>>            placeholder =
>>> self.markdown.htmlStash.store(render_to_string('galleria.html', {
>>> 'images': images }))
>>>            block.clear()
>>>            block.tag = 'p'
>>>            block.text = placeholder
>>>        else:
>>>            b = markdown.util.etree.Element('b')
>>>            b.text = 'There are no images for the given ID'
>>>            return b
>>>
>>>
>>> Should I be using markdown.treeprocessors.Treeprocessor instead of the
>>> inlinepatterns? Can I use it in this way?
>>>
>>
>> You're not returning the placeholder. Try removing the 3 lines with
>> "block" in them and add `return placeholder` in their place. I'd also
>> suggest adding `safe=True` to the call to `htmlStash.store`. Like
>> this:
>>
>>        if images:
>>            placeholder = self.markdown.htmlStash.store(
>>                   render_to_string('galleria.html', {'images': images }),
>>                   safe=True
>>           )
>>            return placeholder
>>        else:
>>            b = markdown.util.etree.Element('b')
>>            b.text = 'There are no images for the given ID'
>>            return b
>>
>> Perhaps I should have pointed out that the CodeHilite extension uses a
>> Blockprocessor, thus the access to the parent "block". That won't work
>> in an inlinepattern (which has no access to the parent). However, if
>> your custom markup is the only thing in a paragraph (on a line by
>> itself), just return the placeholder and you should be done (see below
>> for why). If that doesn't work for you then either a Blockprocessor or
>> Treeprocessor would be the way to go - although it will take more work
>> (code) on your part to detect your custom markup.
>>
>> As a side note, when markdown swaps the htmlStash back in, if a
>> paragraph contains only a placeholder (with nothing else, not even
>> white space, i.e., `<p>some_placeholder</p>`) _and_ the stashed html
>> is block level, then the entire paragraph (`<p>` tag and all) gets
>> replaced with the stashed html. However, in all other situations, only
>> the placeholder itself gets replaced with the stashed html. If your
>> gallery is wrapped in div tags, you probably want the first behavior.
>> Perhaps the relevant code [1] will help you understand what's gong on.
>>
>> [1]: https://github.com/waylan/Python-Markdown/blob/master/markdown/postprocessors.py#L60
>>
>> --
>> ----
>> \X/ /-\ `/ |_ /-\ |\|
>> Waylan Limberg
>
> This worked great. Thank you for your help.

Your welcome.

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

Re: [Python-markdown-discuss] HTML Encoding Issues within Output of Custom Extension

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

On Wed, Jan 18, 2012 at 11:43 AM, andrew thornton
<ath...@gm...> wrote:
> Hello,
>
> I am kind of new to python, but I needed the ability to insert a
> gallery into my django project. I have been working on creating a
> python markdown extension that will insert an image gallery within my
> django project when a custom tag is used. The actual extension is
> working, but the HTML that the extension returns is all encoded. Here
> is the extension that I am using:
>
[snip]
>    class Galleria(markdown.inlinepatterns.Pattern):
>        def handleMatch(self, m):
>            try:
>                images =
> SuperPage.objects.get(id=m.group('superpage_id')).superpageimage_set.all()
>            except:
>                images = None
>            if images:
>                rendered = render_to_string('galleria.html', {
> 'images': images })
>            else:
>                rendered = '<b>There are no images for the given ID</b>'
>            return rendered

Your problem is in the last few lines above. Inlinepatterns must
return ElementTree instances, not strings. Therefore, you need to
build a ET Element (or tree of elements) and return that. For example
consider this abbreviated rewrite of your code:

    if images:
        # build and return gallery here
    else:
        b = markdown.util.etree.Element('b')
        b.text = 'There are no images for the given ID'
        return b

Of course, this means no Django templates for your gallery without a
few workarounds.

A few approaches you might want to look at:

1) Follow the method used by the CodeHilite Extension and save the
html output in the htmlStash (marked as 'safe' so is doesn't get eat
by safe_mode) and return the placeholder. Then the placeholder will be
automatically replaced with the html after the Tree is searialized
into a string. See the code here [1].

2) Parse the html into a ET Tree and return it. But be careful here,
most parsers (including ElementTree's) fall flat on there face with
the simplest of html syntax errors. I would suggest lxml or html5lib,
both of which adds an extra dependency (lxml is the best IMO, but
requires a C lib).  See this excellent comparison [2] of the options.
Just make sure the one you use will build an ET Tree.

[1]: https://github.com/waylan/Python-Markdown/blob/master/markdown/extensions/codehilite.py#L184
[2]: http://blog.ianbicking.org/2008/03/30/python-html-parser-performance/

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

[Python-markdown-discuss] HTML Encoding Issues within Output of Custom Extension

[andrew t. <ath...@gm...>]

Hello,

I am kind of new to python, but I needed the ability to insert a
gallery into my django project. I have been working on creating a
python markdown extension that will insert an image gallery within my
django project when a custom tag is used. The actual extension is
working, but the HTML that the extension returns is all encoded. Here
is the extension that I am using:

    #!/usr/bin/env python
    from django.template.loader import render_to_string
    from main.models import *

    import markdown

    version = "0.1.0"

    class GalleriaExtension(markdown.Extension):
        def __init__(self, configs):
            self.config = {
            }

            # Override defaults with user settings
            for key, value in configs:
                self.setConfig(key, value)

        def add_inline(self, md, name, klass, re):
            pattern = klass(re)
            pattern.md = md
            pattern.ext = self
            md.inlinePatterns.add(name, pattern, "<reference")

        def extendMarkdown(self, md, md_globals):
            self.add_inline(md, 'galleria', Galleria,
                r'\[\[(G|g)allery (?P<superpage_id>\w+)\]\]')

    class Galleria(markdown.inlinepatterns.Pattern):
        def handleMatch(self, m):
            try:
                images =
SuperPage.objects.get(id=m.group('superpage_id')).superpageimage_set.all()
            except:
                images = None
            if images:
                rendered = render_to_string('galleria.html', {
'images': images })
            else:
                rendered = '<b>There are no images for the given ID</b>'
            return rendered

    def makeExtension(configs=None) :
        return GalleriaExtension(configs=configs)

I ensured that django's render_to_string was actually returning html
that was not encoded. From the shell here is an example of the output:

Output from render_to_string:

    >>> from django.template.loader import render_to_string
    >>> images = SuperPage.objects.get(id=8).superpageimage_set.all()
    >>> render_to_string('galleria.html', { 'images': images })
    u'<div class=\'galleria_std\'>\n    <div class=\'gallery\' >\n
 <div id=\'stage_gallery\' >\n'

Here is output from markdown extension that is encoded:

    >>>markdown.markdown('test [[gallery 8]] test', ['galleria'])
    u'<p>test &lt;div class=\'galleria_std\'&gt;\n    &lt;div
class=\'gallery\' &gt;\n'


How can I make rendered return HTML mark up instead of encoded markup
when using the markdown extension? Also, I would appreciate any
pointers on coding this differently (syntax, layout, etc). I
appreciate it.

Thanks

Re: [Python-markdown-discuss] Ability to entirely ignore a block?

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

Text contained inside a raw html block (<div> or <p> for example) is
passed through untouched. You may try that.

Or if you don't want to wrap your block in raw html, take a look at
the code the does that for ideas for your own extension. The output of
the codehilite extension is also ignored in the same way. Both store
the text in the htmlStash instance attached to the Markdown class.
Make sure to mark it "safe" so it's not lost if safe_mode is on.

On Wed, Jan 11, 2012 at 8:10 AM, Ali Afshar <af...@go...> wrote:
> Hi,
>
> We have a use-case where there is some processing of the document
> occurring after the markdown conversion to html, and we are keen for
> the the markdown parser to entirely ignore a block, i.e., to pass
> through entirely untouched.
>
> Is this currently possible? If not what would be the most effective
> way to write an extension to achieve it?
>
> Thanks for your help
>
> --
> Ali Afshar | www.googplus.org/ali | Google Developer Relations
>
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss



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

[Python-markdown-discuss] Ability to entirely ignore a block?

[Ali A. <af...@go...>]

Hi,

We have a use-case where there is some processing of the document
occurring after the markdown conversion to html, and we are keen for
the the markdown parser to entirely ignore a block, i.e., to pass
through entirely untouched.

Is this currently possible? If not what would be the most effective
way to write an extension to achieve it?

Thanks for your help

-- 
Ali Afshar | www.googplus.org/ali | Google Developer Relations

Re: [Python-markdown-discuss] Performance issues with 2.1.0

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

On Wed, Dec 14, 2011 at 10:18 PM, Waylan Limberg <wa...@gm...> wrote:
> Not something I have time for right now. At least we know
> what is causing the slowdown.

Oh, I just created a issue on github to track this so I don't forget it:

https://github.com/waylan/Python-Markdown/issues/59

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

Re: [Python-markdown-discuss] Performance issues with 2.1.0

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

Alex,

I just reverted the rawhtmlblock preprocessor and it is definitely
faster on docs with lots of html.

I pushed a commit to github on the slowhtml [1] branch.  See the diff
here [2]. I should note that a number of tests are failing and not
just the test for the new support of attr in raw html. One test is
even raising an exception. Every change to that file since the
original commit needs to be reviewed and possibly reimplemented before
this code could be considered stable.

That said, I'm not intending on committing this to master anyway. We
don't want to lose support for attributes in raw html. Perhaps a more
efficient solution than the current (long) regex would be the way
forward. Not something I have time for right now. At least we know
what is causing the slowdown.

[1]: https://github.com/waylan/Python-Markdown/tree/slowhtml
[2]: https://github.com/waylan/Python-Markdown/commit/790aeb56053940f299d600d8d364fc3fc8151085

On Wed, Dec 14, 2011 at 5:48 PM, Alexandre Leray
<new...@al...> wrote:
> Thanks Waylan for looking into this, much appreciate.
>
> waiting to hear from you,
>
> Thanks,
>
> Alex
>
>
> On 14/12/2011 22:03, Waylan Limberg wrote:
>>
>> No I hadn't. My unscientific observations were that 2.1.0 might be
>> slightly faster. However, I don't do much raw html myself. In any
>> event, my first guess would be that the cause is the changes made here
>> [1] and here [2], which addressed this issue [3]. I'll try confirming
>> that later tonight.
>>
>> I suggest reporting it on Github [4] so we don't forget about it.
>>
>> [1]:
>> https://github.com/waylan/Python-Markdown/commit/fc3020c68575042a1ff5426ddd94bc4be65bf77d
>> [2]:
>> https://github.com/waylan/Python-Markdown/commit/c2d50b46b536a440b6d73c6bf309bdaf03b90abb
>> [3]: http://www.freewisdom.org/projects/python-markdown/Tickets/000048
>> [4]: https://github.com/waylan/Python-Markdown/issues/new
>
>



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

Re: [Python-markdown-discuss] Performance issues with 2.1.0

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

On Wed, Dec 14, 2011 at 3:34 PM, Alexandre Leray
<new...@al...> wrote:
> Dear all,
>
> there seems to be pretty big performance issues in version 2.1.0,
> especially when dealing with raw HTML. Has anyone noticed it?
>
> Have a look at the test script located at
> <http://stdin.fr/markdown/markdown_issue/>

No I hadn't. My unscientific observations were that 2.1.0 might be
slightly faster. However, I don't do much raw html myself. In any
event, my first guess would be that the cause is the changes made here
[1] and here [2], which addressed this issue [3]. I'll try confirming
that later tonight.

I suggest reporting it on Github [4] so we don't forget about it.

[1]: https://github.com/waylan/Python-Markdown/commit/fc3020c68575042a1ff5426ddd94bc4be65bf77d
[2]: https://github.com/waylan/Python-Markdown/commit/c2d50b46b536a440b6d73c6bf309bdaf03b90abb
[3]: http://www.freewisdom.org/projects/python-markdown/Tickets/000048
[4]: https://github.com/waylan/Python-Markdown/issues/new


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

[Python-markdown-discuss] Performance issues with 2.1.0

[Alexandre L. <new...@al...>]

Dear all,

there seems to be pretty big performance issues in version 2.1.0, 
especially when dealing with raw HTML. Has anyone noticed it?

Have a look at the test script located at 
<http://stdin.fr/markdown/markdown_issue/>

Using markdown==2.0.3:

     python2 markdown_issue.py  0,17s user 0,01s system 94% cpu 0,191 total

Using markdown==2.1.0:

     python2 markdown_issue.py  3,00s user 0,03s system 99% cpu 3,048 total

And it gets worth with the longer files I deal with... I even get stuck 
indefinitely. Unfortunately it is very inconvenient for me switch back 
to 2.0.x as I rely a lot on new style attribute list... Do you have any 
idea on what is going on?

Thanks a lot,

-- Alex

Re: [Python-markdown-discuss] Python-Markdown 2.1.0 released.

[stdin <ec...@st...>]

Dear all,

there seems to be pretty big performance issues in version 2.1.0, 
especially when dealing with raw HTML. Has anyone noticed it?

Alex

On 25/11/2011 13:25, Alexandre Leray wrote:
> Congratulations!
>
> I have been testing the beta; this release is very exciting :)
>
> Thanks for all the good work,
>
> -- Alex
>
>
> On 24/11/2011 21:43, Waylan Limberg wrote:
>> Just letting everyone know that I just released Python-Markdown 
>> 2.1.0.final.
>>
>> Get from PyPi: http://pypi.python.org/pypi/Markdown/2.1.0
>>
>> Read the release notes on github:
>> https://github.com/waylan/Python-Markdown/blob/master/docs/release-2.1.0.md 
>>
>>
> _______________________________________________
> Markdown-Discuss mailing list
> Mar...@si...
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>

-- 
<stdin>
Alexandre Leray&  Stéphanie Vilayphiou
http://stdin.fr/
+32 (0)4 89 00 88 59

Re: [Python-markdown-discuss] Python-Markdown 2.1.0 released.

[Alexandre L. <new...@al...>]

Congratulations!

I have been testing the beta; this release is very exciting :)

Thanks for all the good work,

-- Alex


On 24/11/2011 21:43, Waylan Limberg wrote:
> Just letting everyone know that I just released Python-Markdown 2.1.0.final.
>
> Get from PyPi: http://pypi.python.org/pypi/Markdown/2.1.0
>
> Read the release notes on github:
> https://github.com/waylan/Python-Markdown/blob/master/docs/release-2.1.0.md
>

[Python-markdown-discuss] Python-Markdown 2.1.0 released.

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

Just letting everyone know that I just released Python-Markdown 2.1.0.final.

Get from PyPi: http://pypi.python.org/pypi/Markdown/2.1.0

Read the release notes on github:
https://github.com/waylan/Python-Markdown/blob/master/docs/release-2.1.0.md

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

[Python-markdown-discuss] Python-Markdown 2.1.0-Beta Released

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

I've just released Python-Markdown 2.1.0-Beta.

Get is here: https://github.com/waylan/Python-Markdown/downloads

Release Notes: https://github.com/waylan/Python-Markdown/blob/master/docs/release-2.1.0.md

Report Bugs: https://github.com/waylan/Python-Markdown/issues

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

Re: [Python-markdown-discuss] Sections and other styling options

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

Interesting. Hope you don't mind, but I just added this to the list of
third party extensions.

http://www.freewisdom.org/projects/python-markdown/Available_Extensions

On Sat, Aug 20, 2011 at 10:02 AM, Alexandre Leray
<new...@al...> wrote:
> Hi Igor,
>
> [this][1] might be close to what you are looking for:
>
> -- Alex
>
> [1]:
> http://git.constantvzw.org/?p=aa.core.git;a=blob;f=aacore/mdx_addsections.py;h=969e520a42b0018a2c4b74889fecc83a7dd7704a;hb=HEAD
>
> On 20/08/2011 03:19, Igor Galić wrote:
>> Hi folks,
>>
>> I'm working with a CMS which uses (python) Markdown as basis
>> and I'm a little unhappy with the styling option that it offers.
>>
>> We end up with a
>>
>> <div id="content">
>>   $mardowntext
>> </div>
>>
>> And that is quite difficult to style sensibly.
>>
>> Is there any sane way -- other than wrapping a section with divs
>>
>> <div class="section">
>> # Header # {#header1}
>> Some text here
>> </div>
>>
>> to achieve such an effect?
>> I've been contemplating to add an extension for that purpose,
>> which creates such section and subsection class divs, but my
>> Python-fu is quite poor.
>>
>> Is anyone aware of such a thing already in existence? Or a
>> sensible alternative? Or is putting HTML content the only
>> sensible solution?
>>
>> Thank you for your feedback.
>>
>> So long,
>> i
>
>
> ------------------------------------------------------------------------------
> Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
> user administration capabilities and model configuration. Take
> the hassle out of deploying and managing Subversion and the
> tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



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

Re: [Python-markdown-discuss] Sections and other styling options

[Alexandre L. <new...@al...>]

Hi Igor,

[this][1] might be close to what you are looking for:

-- Alex

[1]: 
http://git.constantvzw.org/?p=aa.core.git;a=blob;f=aacore/mdx_addsections.py;h=969e520a42b0018a2c4b74889fecc83a7dd7704a;hb=HEAD

On 20/08/2011 03:19, Igor Galić wrote:
> Hi folks,
>
> I'm working with a CMS which uses (python) Markdown as basis
> and I'm a little unhappy with the styling option that it offers.
>
> We end up with a
>
> <div id="content">
>   $mardowntext
> </div>
>
> And that is quite difficult to style sensibly.
>
> Is there any sane way -- other than wrapping a section with divs
>
> <div class="section">
> # Header # {#header1}
> Some text here
> </div>
>
> to achieve such an effect?
> I've been contemplating to add an extension for that purpose,
> which creates such section and subsection class divs, but my
> Python-fu is quite poor.
>
> Is anyone aware of such a thing already in existence? Or a
> sensible alternative? Or is putting HTML content the only
> sensible solution?
>
> Thank you for your feedback.
>
> So long,
> i

Re: [Python-markdown-discuss] Sections and other styling options

[Alexandre L. <new...@al...>]

Hi Igor,

this might be close to what you are looking for:

<http://git.constantvzw.org/?p=aa.core.git;a=blob;f=aacore/mdx_addsections.py;h=969e520a42b0018a2c4b74889fecc83a7dd7704a;hb=HEAD>

-- Alex

On 20/08/2011 03:19, Igor Galić wrote:
> Hi folks,
>
> I'm working with a CMS which uses (python) Markdown as basis
> and I'm a little unhappy with the styling option that it offers.
>
> We end up with a
>
> <div id="content">
>   $mardowntext
> </div>
>
> And that is quite difficult to style sensibly.
>
> Is there any sane way -- other than wrapping a section with divs
>
> <div class="section">
> # Header # {#header1}
> Some text here
> </div>
>
> to achieve such an effect?
> I've been contemplating to add an extension for that purpose,
> which creates such section and subsection class divs, but my
> Python-fu is quite poor.
>
> Is anyone aware of such a thing already in existence? Or a
> sensible alternative? Or is putting HTML content the only
> sensible solution?
>
> Thank you for your feedback.
>
> So long,
> i