python-markdown-discuss — A general purpose discussion list

Re: [Python-markdown-discuss] [Plone-Users] ZopeSkel version pinning invalid

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

Waylan released a new version (2.0.3) a few days ago. Did this fix the problem?

- yuri

On Sat, Oct 10, 2009 at 4:19 PM, kiorky <ki...@cr...> wrote:
> Hi waylan,
> Any Status ... !?
>
> kiorky a écrit :
>> Hi Waylan,
>>
>> Some news from python24 packaging front ;).
>>
>> Attached patch make your Markdown package python-2.4 friendly.
>> Feel free to merge/release it.
>>
>> The enjoying console output from the new dist and python 2.4:
>>
>> (test)kiorky@judith ~/projects/repos/python-markdown $ easy_install
>> dist/Markdown-2.0.3.zip
>> Processing Markdown-2.0.3.zip
>> ...
>> Installed
>> /home/kiorky/projects/repos/python-markdown/test/lib/python2.4/site-packages/Markdown-2.0.3-py2.4.egg
>> Processing dependencies for Markdown==2.0.3
>> Searching for elementtree
>> ...
>> Adding elementtree 1.2.7-20070827-preview to easy-install.pth file
>> Installed
>> ...
>> Finished processing dependencies for Markdown==2.0.3
>>
>> (test)kiorky@judith ~/projects/repos/python-markdown $ python -c "import
>> markdown;print markdown.version"
>> 2.0.3
>>
>>
>> cewing a écrit :
>>> kiorky wrote:
>>>> I think the fix must be upstream and the author is quite responsive,
>>>> just advertise him (i already did a bit earlier and im waiting for
>>>> response).
>>>>
>>> As it turns out, we agree with your assessment completely.  The problem lies
>>> upstream and should properly be fixed there.  There's quite a decent
>>> analysis of the problem in
>>> http://www.coactivate.org/projects/zopeskel-bbq-sprint/blog/2009/10/03/zopeskel-bbq-sprint-day-one/
>>> this blog post  from the first day of the zopeskel spring (underway right
>>> now).
>>>
>>> However, the installation of ZopeSkel 2.12 under python 2.4 was broken and
>>> as it is used widely in the zope/plone world, leaving it in that state until
>>> an upstream fix is made is not an option.  We repaired the problem with
>>> ZopeSkel by pinning a version of Cheetah that avoids the whole mess.  This
>>> will solve a truly bad problem for 99% of the folks who use ZopeSkel.
>>>
>>> It appears that you are in the remaining 1% for whom the solution has caused
>>> another problem.  Luckily, there are simple fixes available for you.  You
>>> can pin the version of Cheetah in your package to match that in ZopeSkel
>>> (which is what you've done).  Or you can remove the explicit dependency on
>>> Cheetah and allow the dependency in ZopeSkel to install it for you.
>>>
>>> As
>>> http://www.coactivate.org/projects/zopeskel-bbq-sprint/blog/2009/10/03/zopeskel-bbq-sprint-day-one/
>>> the blog post linked above  states, we agree that the fix should be
>>> upstream.  We have plans to move on to making that fix next.  If you have
>>> the time, we'd welcome your help in getting Markdown repaired so that it can
>>> be installed in python 2.4.  As soon as that fix is made, we will unpin
>>> ZopeSkel and everyone can go along their merry way.
>>>
>>> Thanks,
>>>
>>> c
>>
>>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
>> http://p.sf.net/sfu/devconf
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Plone-Users mailing list
>> Plo...@li...
>> https://lists.sourceforge.net/lists/listinfo/plone-users
>
> --
> --
> Cordialement,
> KiOrKY
> GPG Key FingerPrint: 0x1A1194B7681112AF
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>
>

Re: [Python-markdown-discuss] [Plone-Users] ZopeSkel version pinning invalid

[kiorky <ki...@cr...>]

Hi waylan,
Any Status ... !?

kiorky a écrit :
> Hi Waylan,
> 
> Some news from python24 packaging front ;).
> 
> Attached patch make your Markdown package python-2.4 friendly.
> Feel free to merge/release it.
> 
> The enjoying console output from the new dist and python 2.4:
> 
> (test)kiorky@judith ~/projects/repos/python-markdown $ easy_install
> dist/Markdown-2.0.3.zip
> Processing Markdown-2.0.3.zip
> ...
> Installed
> /home/kiorky/projects/repos/python-markdown/test/lib/python2.4/site-packages/Markdown-2.0.3-py2.4.egg
> Processing dependencies for Markdown==2.0.3
> Searching for elementtree
> ...
> Adding elementtree 1.2.7-20070827-preview to easy-install.pth file
> Installed
> ...
> Finished processing dependencies for Markdown==2.0.3
> 
> (test)kiorky@judith ~/projects/repos/python-markdown $ python -c "import
> markdown;print markdown.version"
> 2.0.3
> 
> 
> cewing a écrit :
>> kiorky wrote:
>>> I think the fix must be upstream and the author is quite responsive,
>>> just advertise him (i already did a bit earlier and im waiting for
>>> response).
>>>
>> As it turns out, we agree with your assessment completely.  The problem lies
>> upstream and should properly be fixed there.  There's quite a decent
>> analysis of the problem in 
>> http://www.coactivate.org/projects/zopeskel-bbq-sprint/blog/2009/10/03/zopeskel-bbq-sprint-day-one/
>> this blog post  from the first day of the zopeskel spring (underway right
>> now).  
>>
>> However, the installation of ZopeSkel 2.12 under python 2.4 was broken and
>> as it is used widely in the zope/plone world, leaving it in that state until
>> an upstream fix is made is not an option.  We repaired the problem with
>> ZopeSkel by pinning a version of Cheetah that avoids the whole mess.  This
>> will solve a truly bad problem for 99% of the folks who use ZopeSkel.
>>
>> It appears that you are in the remaining 1% for whom the solution has caused
>> another problem.  Luckily, there are simple fixes available for you.  You
>> can pin the version of Cheetah in your package to match that in ZopeSkel
>> (which is what you've done).  Or you can remove the explicit dependency on
>> Cheetah and allow the dependency in ZopeSkel to install it for you.
>>
>> As 
>> http://www.coactivate.org/projects/zopeskel-bbq-sprint/blog/2009/10/03/zopeskel-bbq-sprint-day-one/
>> the blog post linked above  states, we agree that the fix should be
>> upstream.  We have plans to move on to making that fix next.  If you have
>> the time, we'd welcome your help in getting Markdown repaired so that it can
>> be installed in python 2.4.  As soon as that fix is made, we will unpin
>> ZopeSkel and everyone can go along their merry way.
>>
>> Thanks,
>>
>> c
> 
> 
> ------------------------------------------------------------------------
> 
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Plone-Users mailing list
> Plo...@li...
> https://lists.sourceforge.net/lists/listinfo/plone-users

-- 
--
Cordialement,
KiOrKY
GPG Key FingerPrint: 0x1A1194B7681112AF

[Python-markdown-discuss] Python-Markdown 2.0.3 Released!

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

For those that have noted that 2.0.2 did not actually fix the
ElementTree dependency problem in the setup script when using 2.3 or
2.4, I have just released 2.0.3 which fixes the problem for sure. I
actually removed ElementTree from my install of 2.4 and ran the script
both before and after the fix and confirmed that it actually fixed the
problem this time. Thanks to everyone who reported this.

Sorry it took so long, but I have been with limited connectivity the
past few weeks and don't even have access to my normal dev box to work
on this stuff.

As a side note, I wonder why this is such a problem for those
installing upstream packages. A quick `easy-install elementtree`
before installing the dependent package would have easily worked
around the problem. In fact, our install documents actually suggest
that as the way to install Markdown on older python versions.

As another aside, someone emailed a patch which I did not use. While I
appreciate the help, the patch switched from using distutils to
setuptools. We (or at least I) would rather avoid that mess -
therefore the simple patch I applied instead.

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

Re: [Python-markdown-discuss] [Plone-Users] ZopeSkel version pinning invalid

[kiorky <ki...@cr...>]

Hi Waylan,

Some news from python24 packaging front ;).

Attached patch make your Markdown package python-2.4 friendly.
Feel free to merge/release it.

The enjoying console output from the new dist and python 2.4:

(test)kiorky@judith ~/projects/repos/python-markdown $ easy_install
dist/Markdown-2.0.3.zip
Processing Markdown-2.0.3.zip
...
Installed
/home/kiorky/projects/repos/python-markdown/test/lib/python2.4/site-packages/Markdown-2.0.3-py2.4.egg
Processing dependencies for Markdown==2.0.3
Searching for elementtree
...
Adding elementtree 1.2.7-20070827-preview to easy-install.pth file
Installed
...
Finished processing dependencies for Markdown==2.0.3

(test)kiorky@judith ~/projects/repos/python-markdown $ python -c "import
markdown;print markdown.version"
2.0.3


cewing a écrit :
> 
> kiorky wrote:
>> I think the fix must be upstream and the author is quite responsive,
>> just advertise him (i already did a bit earlier and im waiting for
>> response).
>>
> As it turns out, we agree with your assessment completely.  The problem lies
> upstream and should properly be fixed there.  There's quite a decent
> analysis of the problem in 
> http://www.coactivate.org/projects/zopeskel-bbq-sprint/blog/2009/10/03/zopeskel-bbq-sprint-day-one/
> this blog post  from the first day of the zopeskel spring (underway right
> now).  
> 
> However, the installation of ZopeSkel 2.12 under python 2.4 was broken and
> as it is used widely in the zope/plone world, leaving it in that state until
> an upstream fix is made is not an option.  We repaired the problem with
> ZopeSkel by pinning a version of Cheetah that avoids the whole mess.  This
> will solve a truly bad problem for 99% of the folks who use ZopeSkel.
> 
> It appears that you are in the remaining 1% for whom the solution has caused
> another problem.  Luckily, there are simple fixes available for you.  You
> can pin the version of Cheetah in your package to match that in ZopeSkel
> (which is what you've done).  Or you can remove the explicit dependency on
> Cheetah and allow the dependency in ZopeSkel to install it for you.
> 
> As 
> http://www.coactivate.org/projects/zopeskel-bbq-sprint/blog/2009/10/03/zopeskel-bbq-sprint-day-one/
> the blog post linked above  states, we agree that the fix should be
> upstream.  We have plans to move on to making that fix next.  If you have
> the time, we'd welcome your help in getting Markdown repaired so that it can
> be installed in python 2.4.  As soon as that fix is made, we will unpin
> ZopeSkel and everyone can go along their merry way.
> 
> Thanks,
> 
> c

-- 
--
Cordialement,
KiOrKY
GPG Key FingerPrint: 0x1A1194B7681112AF

Re: [Python-markdown-discuss] Python-Markdown 2.0.2 Released!

[kiorky <ki...@cr...>]

Hi,

The fix is not working, see [1].
Please also note that now, the side effect is that installing ZopeSkel and other
paster dependents things break because ZopeSkel pinning is not valid too...


[1] -
http://www.coactivate.org/projects/zopeskel-bbq-sprint/blog/2009/10/03/zopeskel-bbq-sprint-day-one/


Waylan Limberg a écrit :
> Hey, just letting everyone know I just released Python-Markdown 2.0.2
> [1]. This is a bug-fix release only. In the last 3 days I've received
> 2 complaints regarding the elementtree dependency. Apparently
> Cheetah's most recent release (2.2.2) just changed their dependency on
> Markdown and everyone on older versions of Python (< 2.5) are getting
> errors when easy_installing Cheetah. So I fixed the problem on our end
> and released 2.0.2 to address the issue.
> 
> As a plus, all the various bug-fixes we've committed since the last
> release are included as well. As there have been no significant
> changes, I couldn't see jumping up to 2.1 yet. There are a few things
> in the works though.
> 
> [1]: http://pypi.python.org/pypi/Markdown/2.0.2
> 

-- 
--
Cordialement,
KiOrKY
GPG Key FingerPrint: 0x1A1194B7681112AF

Re: [Python-markdown-discuss] Python-Markdown 2.0.2 Released!

[Youenn B. <you...@in...>]

Thanks a lot Waylan.

Le 28 sept. 09 à 17:08, Waylan Limberg a écrit :

> Hey, just letting everyone know I just released Python-Markdown 2.0.2
> [1]. This is a bug-fix release only. In the last 3 days I've received
> 2 complaints regarding the elementtree dependency. Apparently
> Cheetah's most recent release (2.2.2) just changed their dependency on
> Markdown and everyone on older versions of Python (< 2.5) are getting
> errors when easy_installing Cheetah. So I fixed the problem on our end
> and released 2.0.2 to address the issue.
>
> As a plus, all the various bug-fixes we've committed since the last
> release are included as well. As there have been no significant
> changes, I couldn't see jumping up to 2.1 yet. There are a few things
> in the works though.
>
> [1]: http://pypi.python.org/pypi/Markdown/2.0.2
>
> -- 
> ----
> \X/ /-\ `/ |_ /-\ |\|
> Waylan Limberg

Youenn Boussard
INGENIWEB (TM) - SAS 50000 Euros - RC B 438 725 632
1, rue Royale
227, Les Bureaux de la Colline - Bat D
92213  - Saint Cloud Cedex
Tél : 01 78 15 24 00 / Fax : 01 46 02 44 04

[Python-markdown-discuss] Python-Markdown 2.0.2 Released!

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

Hey, just letting everyone know I just released Python-Markdown 2.0.2
[1]. This is a bug-fix release only. In the last 3 days I've received
2 complaints regarding the elementtree dependency. Apparently
Cheetah's most recent release (2.2.2) just changed their dependency on
Markdown and everyone on older versions of Python (< 2.5) are getting
errors when easy_installing Cheetah. So I fixed the problem on our end
and released 2.0.2 to address the issue.

As a plus, all the various bug-fixes we've committed since the last
release are included as well. As there have been no significant
changes, I couldn't see jumping up to 2.1 yet. There are a few things
in the works though.

[1]: http://pypi.python.org/pypi/Markdown/2.0.2

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

[Python-markdown-discuss] Feedback on Ticket 40 [Tabs & Spaces]

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

A few weeks back someone (silviogutierrez) filed ticket 40 [1] and
claimed that with a particular arrangement of tabs and spaces in a
list Markdown will crash.

Unfortunately, I cannot reproduce this. Obviously, we don't want
Markdown crashing. Therefore, if anyone know's who the reporter is,
please make sure s/he knows s/he needs to respond with more info. Or,
look it over yourself. Perhaps there's something obvious I'm missing.

If the problem can't be reproduced, I'm likely to close the ticket as
"won't fix". But I hate a bury a real problem. Unfortunately, the
ticket tracker doesn't have any automated feedback mechanism (aside
from RSS feed which you manually have to subscribe to), and the
reporter didn't leave an email address, so I don't know of any other
way to contact him/her.

[1]: http://www.freewisdom.org/projects/python-markdown/Tickets/000040

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

Re: [Python-markdown-discuss] lxml.etree? (trying to do something with treeprocessor)

[Mark E. <ei...@gm...>]

On Fri, Aug 21, 2009 at 9:28 AM, Waylan Limberg<wa...@gm...> wrote:
> On Fri, Aug 21, 2009 at 12:09 AM, Mark Eichin<ei...@gm...> wrote:
>> I'd like to write a treeprocessor that takes the <h2> elements and
>> stuffs <a name="..."> anchors before them (with the anchorname derived
>> from the h2 text.)
>
> Why not just set the id on the h2 tag? Like this: `<h2 id="...">`. It
> accomplishes the same thing and is actually considered the correct way
> to do it today. In fact, the HeaderId extension [1] included with
> Markdown already does this.

... because it never occurred to me that there'd be "new" syntax for
that... sure enough,
http://www.w3.org/TR/html401/struct/links.html#h-12.1.1 (amusingly,
that document *itself* still uses <a name="..."> but it puts that
inside the <h3> so it avoids the problem from a different direction.)

(4.01 was published in 1999, so I suppose I can't really call that
"new", can I :-)

> Regarding the issues with ElementTree, yes, unfortunately, ET elements
> have no reference to their parent, thus no knowledge of their
> siblings, which, needless to say is very annoying. Probably my biggest
> gripe. But Yuri's recollection is correct. We initially tried to offer
> lxml as an option but there were just to many differences to make it
> work right with both. I believe lxml's poor Unicode support was a
> problem as well. As Yuri mentioned, search the list archives for more.
> Of course, if we could get it working, I would gladly do so for both
> the performance increase and references to parent elements.

Got it, thanks.

> [1]: http://www.freewisdom.org/projects/python-markdown/HeaderId
>
> --
> ----
> \X/ /-\ `/ |_ /-\ |\|
> Waylan Limberg
>



-- 
_Mark_ <ei...@th...> <ei...@gm...>

Re: [Python-markdown-discuss] lxml.etree? (trying to do something with treeprocessor)

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

On Fri, Aug 21, 2009 at 12:09 AM, Mark Eichin<ei...@gm...> wrote:
> I'd like to write a treeprocessor that takes the <h2> elements and
> stuffs <a name="..."> anchors before them (with the anchorname derived
> from the h2 text.)

Why not just set the id on the h2 tag? Like this: `<h2 id="...">`. It
accomplishes the same thing and is actually considered the correct way
to do it today. In fact, the HeaderId extension [1] included with
Markdown already does this.

Regarding the issues with ElementTree, yes, unfortunately, ET elements
have no reference to their parent, thus no knowledge of their
siblings, which, needless to say is very annoying. Probably my biggest
gripe. But Yuri's recollection is correct. We initially tried to offer
lxml as an option but there were just to many differences to make it
work right with both. I believe lxml's poor Unicode support was a
problem as well. As Yuri mentioned, search the list archives for more.
Of course, if we could get it working, I would gladly do so for both
the performance increase and references to parent elements.

[1]: http://www.freewisdom.org/projects/python-markdown/HeaderId

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

Re: [Python-markdown-discuss] lxml.etree? (trying to do something with treeprocessor)

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

> from the h2 text.)  markdown.etree does give me findall... but the
> Elements I get back don't appear to have any sibling operations that
> would let me do that.

I can't remember right now, but it's possible that ElementTree
interface just doesn't provide that method.

> second is, does it make sense to consider lxml.etree another candidate
> for etree_loader.importETree?  (That would at least give me
> addprevious which does exactly what I'm looking for...)

We did at one point, but found lxml's implementation of ETree to have
a lot of quirks along the lines you mentioned below. (You can search
the list archives for "lxml" to find those discussions.) It may be
worth looking at this again and considering if we can fix those issues
on our end, but at the time, if I remember correctly, it didn't seem
worth it.

Have you considered just traversing the tree top-down once and
inserting all the extra tags that you need?

- yuri

[Python-markdown-discuss] lxml.etree? (trying to do something with treeprocessor)

[Mark E. <ei...@gm...>]

I'd like to write a treeprocessor that takes the <h2> elements and
stuffs <a name="..."> anchors before them (with the anchorname derived
from the h2 text.)  markdown.etree does give me findall... but the
Elements I get back don't appear to have any sibling operations that
would let me do that.

First question is of course "is there a better way to do that"...
second is, does it make sense to consider lxml.etree another candidate
for etree_loader.importETree?  (That would at least give me
addprevious which does exactly what I'm looking for...)

I did try
   import lxml.etree
   markdown.etree = lxml.etree
(right after the "import markdown" itself) which got a couple of
FutureWarnings and a fatal complaint about null bytes in strings, so
it doesn't Just Work...

--
_Mark_ <ei...@th...> <ei...@gm...>

Re: [Python-markdown-discuss] Emphasis inside brackets -- bug?

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

I've just pushed a fix for this:

http://gitorious.org/python-markdown/mainline/commit/383916493d8d05feb8df72e61cbec15d9b5fb937

On Fri, Jul 17, 2009 at 11:59 AM, seanh<sea...@gm...> wrote:
> I noticed that Python-Markdown doesn't seem to convert (_emphasis
> immediately surrounded by brackets_). Is this a bug?
>
> ------------------------------------------------------------------------------
> Enter the BlackBerry Developer Challenge
> This is your chance to win up to $100,000 in prizes! For a limited time,
> vendors submitting new applications to BlackBerry App World(TM) will have
> the opportunity to enter the BlackBerry Developer Challenge. See full prize
> details at: http://p.sf.net/sfu/Challenge
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



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

Re: [Python-markdown-discuss] Emphasis inside brackets -- bug?

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

On Sun, Jul 19, 2009 at 9:58 PM, Waylan Limberg<wa...@gm...> wrote:
> Yeah, it would appear so:
>
> http://babelmark.bobtfish.net/?markdown=[_foo_]
>
> Thanks for the report. I've filed a new ticket so we don't forget this:
>
> http://www.freewisdom.org/projects/python-markdown/Tickets/000002

FYI, due to a bug in the ticket tracker (just fixed), this is now ticket 38:

http://www.freewisdom.org/projects/python-markdown/Tickets/000038

Look for any updates there. Sorry for any confusion this may have caused.

> On Fri, Jul 17, 2009 at 11:59 AM, seanh<sea...@gm...> wrote:
>> I noticed that Python-Markdown doesn't seem to convert (_emphasis
>> immediately surrounded by brackets_). Is this a bug?
>>

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

Re: [Python-markdown-discuss] Emphasis inside brackets -- bug?

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

Yeah, it would appear so:

http://babelmark.bobtfish.net/?markdown=[_foo_]

Thanks for the report. I've filed a new ticket so we don't forget this:

http://www.freewisdom.org/projects/python-markdown/Tickets/000002

On Fri, Jul 17, 2009 at 11:59 AM, seanh<sea...@gm...> wrote:
> I noticed that Python-Markdown doesn't seem to convert (_emphasis
> immediately surrounded by brackets_). Is this a bug?
>
> ------------------------------------------------------------------------------
> Enter the BlackBerry Developer Challenge
> This is your chance to win up to $100,000 in prizes! For a limited time,
> vendors submitting new applications to BlackBerry App World(TM) will have
> the opportunity to enter the BlackBerry Developer Challenge. See full prize
> details at: http://p.sf.net/sfu/Challenge
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



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

[Python-markdown-discuss] Emphasis inside brackets -- bug?

[seanh <sea...@gm...>]

I noticed that Python-Markdown doesn't seem to convert (_emphasis
immediately surrounded by brackets_). Is this a bug?

Re: [Python-markdown-discuss] Location of m ptarkdown plugin changed

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

On Tue, Jul 14, 2009 at 8:05 AM, <se...@la...> wrote:
> Sorry about this but I wanted to promote the pyblosxom plugin for
> python-markdown to a full project on github (with history) rather than
> just a gist, so it's now moved to:
>
> http://github.com/seanh/PyBlosxom-Python-Markdown-2-Plugin
>
> There is no functional change. The integration page of the python-markdown
> site will need to be updated.
>

Thanks for the update. I've updated the link.

A few thinks. I notice that you keep referring to "Python-Markdown 2".
You may not be aware that there is a second unrelated project called
"Markdown2", so you might want to change your documentation to refer
to "Python-Markdown v2.0" (or perhaps "v2.x") to keep it more clear.

Second, I couldn't help but notice that you are converting all
documents to acsii before passing them to Markdown. Why? Markdown is
fully Unicode aware (and actually uses Unicode internally). I would
expect that you would want to be converting to Unicode from whatever
encoding the user's files are in. If you look at our tests, we have
entire documents in Russian and Arabic that run through Markdown
without issue. Why limit yourself to only English users?

Regardless, it great to see others benefiting from our project.

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

[Python-markdown-discuss] Location of m ptarkdown plugin changed

[<se...@la...>]

Sorry about this but I wanted to promote the pyblosxom plugin for
python-markdown to a full project on github (with history) rather than
just a gist, so it's now moved to:

http://github.com/seanh/PyBlosxom-Python-Markdown-2-Plugin

There is no functional change. The integration page of the python-markdown
site will need to be updated.

Re: [Python-markdown-discuss] IndexError when using five spaces after asterisk (list)

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

I see. Great then!

  - yuri

On Tue, Jun 23, 2009 at 10:48 PM, Waylan Limberg<wa...@gm...> wrote:
> Hey Yuri,
>
> Actually is was a problem with 2.0. However, I pushed a fix and test
> later that same day (see the last commit on master). Apparently, when
> I informed Mikael of the fix, I failed to copy the list.
>
> On Tue, Jun 23, 2009 at 10:35 PM, Yuri Takhteyev<qar...@gm...> wrote:
>>>> It's real easy to spawn the IndexError exception. Just run:
>>>>
>>>>>>> import markdown
>>>>>>> markdown.markdown("*     five spaces")
>>>
>>> Yeah, that's a problem. I'll look into that when I get a chance.
>>
>> As I understand, the problem only happens with 1.x. Given that 2.0 is
>> out and doesn't suffer from this (I just tested), perhaps the thing to
>> do is to figure out what it takes to make 2.0 work with Django. It
>> can't be that hard.
>>
>> Unfortunately, I am not using Django at the moment, but perhaps
>> someone could help Mikael out?
>>
>>  - yuri
>>
>> --
>> http://spu.tnik.org/
>>
>
>
>
> --
> ----
> \X/ /-\ `/ |_ /-\ |\|
> Waylan Limberg
>



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

Re: [Python-markdown-discuss] IndexError when using five spaces after asterisk (list)

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

Hey Yuri,

Actually is was a problem with 2.0. However, I pushed a fix and test
later that same day (see the last commit on master). Apparently, when
I informed Mikael of the fix, I failed to copy the list.

On Tue, Jun 23, 2009 at 10:35 PM, Yuri Takhteyev<qar...@gm...> wrote:
>>> It's real easy to spawn the IndexError exception. Just run:
>>>
>>>>>> import markdown
>>>>>> markdown.markdown("*     five spaces")
>>
>> Yeah, that's a problem. I'll look into that when I get a chance.
>
> As I understand, the problem only happens with 1.x. Given that 2.0 is
> out and doesn't suffer from this (I just tested), perhaps the thing to
> do is to figure out what it takes to make 2.0 work with Django. It
> can't be that hard.
>
> Unfortunately, I am not using Django at the moment, but perhaps
> someone could help Mikael out?
>
>  - yuri
>
> --
> http://spu.tnik.org/
>



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

Re: [Python-markdown-discuss] IndexError when using five spaces after asterisk (list)

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

>> It's real easy to spawn the IndexError exception. Just run:
>>
>>>>> import markdown
>>>>> markdown.markdown("*     five spaces")
>
> Yeah, that's a problem. I'll look into that when I get a chance.

As I understand, the problem only happens with 1.x. Given that 2.0 is
out and doesn't suffer from this (I just tested), perhaps the thing to
do is to figure out what it takes to make 2.0 work with Django. It
can't be that hard.

Unfortunately, I am not using Django at the moment, but perhaps
someone could help Mikael out?

  - yuri

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

Re: [Python-markdown-discuss] IndexError when using five spaces after asterisk (list)

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

Hey Mikeal, thanks for the report.

On Wed, Jun 17, 2009 at 8:21 AM, Mikael Garde
Nielsen<mg...@ze...> wrote:
[snip]
> It does however render
> differently than what I would expect, so the test still fails.

What did your expect? As it turns out, every impelmentation appears to
render the same. See:

http://babelmark.bobtfish.net/?markdown=*+one%0D%0A*++++four%0D%0A*+++++five

Or did you mean that you expected that output, but got something
different? After running this:

    >>> markdown.markdown('* one\n*     five')

I assume that is what you mean.

>
> It's real easy to spawn the IndexError exception. Just run:
>
>>>> import markdown
>>>> markdown.markdown("*     five spaces")

Yeah, that's a problem. I'll look into that when I get a chance.

For anyone who are interested, I've created a ticket (#35) which
addresses this and all it's variants here:

http://www.freewisdom.org/projects/python-markdown/Tickets/000035

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

[Python-markdown-discuss] IndexError when using five spaces after asterisk (list)

[Mikael G. N. <mg...@ze...>]

* one space
*    four spaces
*     five spaces

Re: [Python-markdown-discuss] IndexError when using five spaces after asterisk (list)

[Mikael G. N. <mg...@ze...>]

<ul>
<li>one space</li>
<li>four spaces</li>
<li>five spaces</li>
</ul>

[Python-markdown-discuss] Version 2.0.1 Released - Command line issues fixed!

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

I've just released python-markdown 2.0.1. Get it here:

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


Python-Markdown 2.0.1 Release Notes
===================================

Python-Markdown 2.0.1 is a bug-fix release. No new features have been added.
Most notably, various issues with the command line script have been fixed.
There have also been a few fixes for minor parsing bugs in some edge cases.
For a full list of changes, see the git log.

Backwards-incompatible Changes
------------------------------

Due to various complications in how Python handles command line scripts in
differance systems and with differant installation tools, we were forced to
rename the commandline script to ``markdown`` (no ".py"). A matching batch
script will get installed on Windows. Any shell scripts which call
``markdown.py`` will need to be altered to call ``markdown`` instead.


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