Re: [Python-markdown-discuss] AtomicString

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

This is done [1].

Btw, if anyone is concerned that that diff removed AtomicString - it
was being defined twice for some reason so I removed one instance.

[1]: http://gitorious.org/projects/python-markdown/repos/mainline/commits/c26816e831df0f8123cd24bd72f352f9f3909ce6

On Wed, Sep 3, 2008 at 11:31 AM, Waylan Limberg <wa...@gm...> wrote:
> On Wed, Sep 3, 2008 at 5:09 AM, Yuri Takhteyev <qar...@gm...> wrote:
>>> Therefore, I propose that we select 2 strings of random chars (using
>>> whatever method you desire) and **hardcode** those 2 strings into
>>> markdown.py. That way, on each import (each page view in the above
>>> scenario) the placeholder strings will be the same and debugging will
>>> be consistent.  What we really want is a string that will never be
>>> matched by another inline pattern's regex. We just need a string of
>>> all same-case chars between a-z of length n. As long as it does not
>>> contain any known words or abbreviations it works for me.
>>> Additionally, if the string is consistent, that makes it easier for an
>>> extension author to write  the regex for inline patterns that will not
>>> match the string in the placeholder.
>>
>> That's exactly what I suggested in my first email to this thread. :)
>>
> And that's exactly what I plan to use once I got the whitespace issues
> work out (I think I got it last night - just need a little more
> testing).
>
>
> --
> ----
> Waylan Limberg
> wa...@gm...
>



-- 
----
Waylan Limberg
wa...@gm...