python-markdown-discuss — A general purpose discussion list

[Python-markdown-discuss] [PATCH] create the test output directory if it doesn't already exist.

[Jeff B. <its...@gm...>]

codecs.open was failing without it.
---
 test-markdown.py |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/test-markdown.py b/test-markdown.py
index e3997a4..bc2b891 100644
--- a/test-markdown.py
+++ b/test-markdown.py
@@ -214,6 +214,9 @@ def testDirectory(dir, measure_time=False, safe_mode=False) :
     except: 
         hd = None
 
+    if not os.path.exists(TMP_DIR):
+        os.mkdir(TMP_DIR)
+
     htmlDiffFilePath = os.path.join(TMP_DIR, os.path.split(dir)[-1]) + ".html"
     htmlDiffFile = codecs.open(htmlDiffFilePath, "w", encoding=encoding)
     htmlDiffFile.write(DIFF_FILE_TEMPLATE)
-- 
1.5.5.1

Re: [Python-markdown-discuss] [PATCH] unwrapping urlparse result tuple manually for python 2.4 compatibility.

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

Thanks.  I pushed this commit.  Sorry about this, not sure when this
has slipped in.  My goal has been to keep compatibility not only with
2.4 but also with 2.3.  I also noticed that while markdown.py works
with 2.3 (well used to, and now again with your patch), the
test-markdown.py script did not.  So, I changed test-markdown.py to
work with 2.3.

So, let's all agree that test-markdown.py should be ran with
python2.3, python2.4 and python2.5 after each change.  If you cannot
check it with all three, then make a commit in a branch and email it
to me so that I could test before merging.

Also, Waylan and David, can you check in test cases for the fixes you
made in the recent months?

BTW, I also noticed that we have a regression on one of the tests.  I
suspect this might be the price we are paying for some of the other
issues that Waylan fixed.  Hopefully we'll resolve this with Artem's
help over the next few months.

  - yuri

On Fri, May 30, 2008 at 2:22 PM, Jeff Balogh <its...@gm...> wrote:
> In 2.5 the result is wrapped in a ParseResult class so that fields can be
> accessed by name, but a plain tuple is returned in 2.4.
> ---
>
> I don't think I've seen any patches on the list yet, but you can apply it with
> git-am.
>
>  markdown.py |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/markdown.py b/markdown.py
> index 3348acc..422cde4 100644
> --- a/markdown.py
> +++ b/markdown.py
> @@ -34,7 +34,7 @@ __revision__ = "$Rev$"
>
>
>  import re, sys, codecs
> -from urlparse import urlparse
> +from urlparse import urlparse, urlunparse
>
>  from logging import getLogger, StreamHandler, Formatter, \
>                     DEBUG, INFO, WARN, ERROR, CRITICAL
> @@ -930,9 +930,9 @@ class LinkPattern (Pattern):
>
>         """
>         locless_schemes = ['', 'mailto', 'news']
> -        url = urlparse(url)
> +        scheme, netloc, path, params, query, fragment = url = urlparse(url)
>         safe_url = False
> -        if url.netloc != '' or url.scheme in locless_schemes:
> +        if netloc != '' or scheme in locless_schemes:
>             safe_url = True
>
>         for part in url[2:]:
> @@ -942,7 +942,7 @@ class LinkPattern (Pattern):
>         if self.safe_mode and not safe_url:
>             return ''
>         else:
> -            return url.geturl()
> +            return urlunparse(url)
>
>  class ImagePattern(LinkPattern):
>     """ Return a NanoDom img Element from the given match. """
> --
> 1.5.5.1
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



-- 
http://sputnik.freewisdom.org/

[Python-markdown-discuss] [PATCH] unwrapping urlparse result tuple manually for python 2.4 compatibility.

[Jeff B. <its...@gm...>]

In 2.5 the result is wrapped in a ParseResult class so that fields can be
accessed by name, but a plain tuple is returned in 2.4.
---

I don't think I've seen any patches on the list yet, but you can apply it with
git-am.

 markdown.py |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/markdown.py b/markdown.py
index 3348acc..422cde4 100644
--- a/markdown.py
+++ b/markdown.py
@@ -34,7 +34,7 @@ __revision__ = "$Rev$"
 
 
 import re, sys, codecs
-from urlparse import urlparse
+from urlparse import urlparse, urlunparse
 
 from logging import getLogger, StreamHandler, Formatter, \
                     DEBUG, INFO, WARN, ERROR, CRITICAL
@@ -930,9 +930,9 @@ class LinkPattern (Pattern):
         
         """
         locless_schemes = ['', 'mailto', 'news']
-        url = urlparse(url)
+        scheme, netloc, path, params, query, fragment = url = urlparse(url)
         safe_url = False
-        if url.netloc != '' or url.scheme in locless_schemes:
+        if netloc != '' or scheme in locless_schemes:
             safe_url = True
 
         for part in url[2:]:
@@ -942,7 +942,7 @@ class LinkPattern (Pattern):
         if self.safe_mode and not safe_url:
             return ''
         else:
-            return url.geturl()
+            return urlunparse(url)
 
 class ImagePattern(LinkPattern):
     """ Return a NanoDom img Element from the given match. """
-- 
1.5.5.1

Re: [Python-markdown-discuss] Header parsing doesn't match the original Markdown...

[John S. <jo...@sz...>]

On Wed, May 14, 2008 at 11:31 PM, Waylan Limberg <wa...@gm...> wrote:
> Thanks John. I've applied your patch, which is available here:
> http://gitorious.org/projects/python-markdown/repos/mainline/commits/a91e308363eeacd77270cdcb3df2109e0cfe2d18

Thanks!

-John

Re: [Python-markdown-discuss] Header parsing doesn't match the original Markdown...

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

Thanks John. I've applied your patch, which is available here:
http://gitorious.org/projects/python-markdown/repos/mainline/commits/a91e308363eeacd77270cdcb3df2109e0cfe2d18

On Wed, May 14, 2008 at 10:50 PM, John Szakmeister <jo...@sz...> wrote:
> I've been moving my blog to Django, and decided to use the Markdown
> syntax... so I've been using your library.  I ran into a problem where
> it was unhappy about a header in one of the posts.  In particular, it
> didn't like a hash being in the middle of the header.  Gruber's
> implementation accepts it fine though, and nothing says that it's
> incorrect.  So, I made a patch that makes python markdown match the
> Perl version more closely and adds a test in the test suite for it.
>
> If you have any questions or feedback, please CC me as I'm not
> subscribed to the list.
>
> Thanks!
>
> -John
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>
>



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

[Python-markdown-discuss] Header parsing doesn't match the original Markdown...

[John S. <jo...@sz...>]

I've been moving my blog to Django, and decided to use the Markdown
syntax... so I've been using your library.  I ran into a problem where
it was unhappy about a header in one of the posts.  In particular, it
didn't like a hash being in the middle of the header.  Gruber's
implementation accepts it fine though, and nothing says that it's
incorrect.  So, I made a patch that makes python markdown match the
Perl version more closely and adds a test in the test suite for it.

If you have any questions or feedback, please CC me as I'm not
subscribed to the list.

Thanks!

-John

[Python-markdown-discuss] Fenced-Code-Blocks in Python-Markdown

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

I'd like to announce a beta release of the Fenced-Code-Blocks
Extension for Python-Markdown.

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

The latest code for Python-Markdown and packaged extensions are now
available on Gitorious.

<http://gitorious.org/projects/python-markdown>

The same syntax is used as the just released PHP Markdown Extra 1.2. I
did add the option to define a class on the block for language
identification. Here's an example:

    ~~~~~~~~~~~~
    <p>Hello World!</p>
    ~~~~~~~~~~~~{.html}

Becomes:

    <pre><code class="html">&lt;p&gt;Hello World!&lt;/p&gt;
    </code></pre>

This should work nicely with Highlight.js [1] if one so desires. Of
course, as this is optional, if you leave the class definition off, it
works like PHP Markdown Extra. Unfortunately, including the class
definition makes PHP Markdown Extra fail to match the block. Consider
yourself warned.

[1]: http://softwaremaniacs.org/soft/highlight/en/



On Sun, May 11, 2008 at 8:31 AM, Michel Fortin
<mic...@mi...> wrote:
[snip]
>
> This new version of PHP Markdown Extra adds support for "fenced" code blocks
> (which I was previously calling "flat"). Fenced code blocks overcome many
> limitations of Markdown's indented code blocks: they can can be put
> immediately following a list item, can start and end with blank lines, and
> can be put one after the other as two consecutive code blocks. Also, if
> you're using an editor which cannot indent automatically a selected block of
> text, such as a text box in your web browser, it's easier to paste code in.
>
[snip]
>
> Extra 1.2 (11 May 2008):
>
> *       Added fenced code block syntax which don't require indentation
>        and can start and end with blank lines. A fenced code block
>        starts with a line of consecutive tilde (~) and ends on the
>        next line with the same number of consecutive tilde. Here's an
>        example:
>
>            ~~~~~~~~~~~~
>            Hello World!
>            ~~~~~~~~~~~~
>
[snip]



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

Re: [Python-markdown-discuss] mdx_tables bug

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

>  As I was typing my response, this occurred to me as well. Perhaps at
>  the least we should provide a public method that wraps the private
>  method. Something like, handleInline(*args  **kwargs). That way, it is
>  both backward and forward compatible. However, I believe the gSOC
>  project will be addressing the inline patterns directly, so perhaps we
>  should wait and see what comes out of that before setting a new API.

This makes sense.  Let's put this on the list of things to do when we
do refactoring.  I think we need a public method there, but I am not
sure of top of my head which method should be made public.

>  Cool! Any reason why you didn't commit the latest versions of my
>  extensions (wikilink & codehilite)? I'll update them if you didn't
>  have any specific reason.

I just checked in what I had at the moment.  Feel free to add/update.

>  Anyway while were at it, mind if I add some more (I have 7 total) to
>  the mainline or would you prefer elsewhere for now?

I would like to avoid creating an expectation that all extensions must
be in the same place.  If people want to write extensions and maintain
those extensions themselves in their own code repository, that's quite
fine by me.  Furthermore, I really cannot commit to maintaining
extensions that I didn't write.

So, I think our gitorious repository is the best place for extensions
that either one of us is maintaining or extensions that look
abandoned.  For extensions that have a maintainer, I would prefer to
leave it up to the maintainer where they want to host it.  Which means
we'll have to do it on a case by case basis.

  - yuri

-- 
http://sputnik.freewisdom.org/

[Python-markdown-discuss] Fwd: Markdown Extra Specification (First Draft)

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

We'll have to figure out how to factor this into the planned python
markdown refactoring...  Note that Michel is only planning on finish
this document in July and to add the parsing part by 2009.  That won't
fit too well with Artem's GSoC schedule.

  - yuri

---------- Forwarded message ----------
From: Michel Fortin <mic...@mi...>
Date: Mon, May 5, 2008 at 7:33 PM
Subject: Markdown Extra Specification (First Draft)
To: "Discussion related to Markdown." <mar...@si...>


It took much more time than I expected, and it is currently less
complete than I have hoped, but I've finaly made a first draft of the
Markdown Extra spec. You can find it at
<http://michelf.com/specs/markdown-extra/>

 Currently, the specification defines its goals and a document model
for Markdown Extra. It lacks the most important part though: the
parsing section, which I'm going to write next. As I update the
document locally on my computer, I'll update the public specification
page to always reflect the latest version.

 I'm working on this on my free time, alongside a full-time job, a few
other projects, and other duties. I'm hoping to have a draft of the
parsing section covering all parts of the syntax by July, and to have
completed the whole specification by 2009. I'm not sure of how
realistic this timetable is, but we'll see.

 To take part in this work, simply leave your comments, suggestions,
and potential issues on this list, or send them to me by private email
if you don't want your comment to be public for some reason.


-- 
http://sputnik.freewisdom.org/

Re: [Python-markdown-discuss] mdx_tables bug

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

Bah, I failed to copy the list with my response. Here it is:

On Fri, May 2, 2008 at 11:33 AM, Waylan Limberg <wa...@gm...> wrote:
> Glin, thanks for your report. Personally, I have never used that
>  extension and don't even know if it works.
>
>  In any event, regarding your comments about _handleInline and
>  _handleInlineWrapper; those methods have been in flux. It used to be
>  that there was only _handleInline. Then _handleInlineWrapper was added
>  to wrap the first method. Later, the wrapper stopped calling
>  _handleInline altogether and did everything on it's own. As
>  _handleInline was still in the code, but (mostly) unused, this caused
>  all sorts of confusion.
>
>  Therefore in the latest release (1.7) the unused code was removed and
>  there is only one method _handleInline. I'd suggest upgrading to the
>  latest release of markdown and then see how it works.
>
>

On Fri, May 2, 2008 at 1:44 PM, Yuri Takhteyev <qar...@gm...> wrote:
> >  IMHO this extension shouldn't use _handleInline method, but
>  >  _handleInlineWrapper2. I went through the source code of markdown and it
>  >  appears, that _handleInline is only some 'private' function used by
>  >  _handleInlineWrapper2 - so _handleInline applies only one pattern and
>  >  returns chunks in reverse order, which is completely wrong and will do
>  >  mess when you use any inline pattern in table.
>
>  Thanks for pointing this out.  Strictly speaking, the extensions
>  shouldn't be using an of the _... methods.  So, we should probably
>  think whether this is a sign that we need to expose a bit more of the
>  API.  Anyway, I'll try to look into this.

As I was typing my response, this occurred to me as well. Perhaps at
the least we should provide a public method that wraps the private
method. Something like, handleInline(*args  **kwargs). That way, it is
both backward and forward compatible. However, I believe the gSOC
project will be addressing the inline patterns directly, so perhaps we
should wait and see what comes out of that before setting a new API.

>
>
>  >  I don't have permission to wiki so I cannot write it there, so I'm
>  >  sending this email to mailinglist.
>
>  We switched to git last week and I just checked in additional
>  extensions that I have, including this one.
>
>  The project is at http://gitorious.org/projects/python-markdown/ and
>  the "mainline" repository is at
>  http://gitorious.org/projects/python-markdown/repos/mainline/
>
Cool! Any reason why you didn't commit the latest versions of my
extensions (wikilink & codehilite)? I'll update them if you didn't
have any specific reason.

Anyway while were at it, mind if I add some more (I have 7 total) to
the mainline or would you prefer elsewhere for now?



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

Re: [Python-markdown-discuss] mdx_tables bug

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

>  IMHO this extension shouldn't use _handleInline method, but
>  _handleInlineWrapper2. I went through the source code of markdown and it
>  appears, that _handleInline is only some 'private' function used by
>  _handleInlineWrapper2 - so _handleInline applies only one pattern and
>  returns chunks in reverse order, which is completely wrong and will do
>  mess when you use any inline pattern in table.

Thanks for pointing this out.  Strictly speaking, the extensions
shouldn't be using an of the _... methods.  So, we should probably
think whether this is a sign that we need to expose a bit more of the
API.  Anyway, I'll try to look into this.

>  I don't have permission to wiki so I cannot write it there, so I'm
>  sending this email to mailinglist.

We switched to git last week and I just checked in additional
extensions that I have, including this one.

The project is at http://gitorious.org/projects/python-markdown/ and
the "mainline" repository is at
http://gitorious.org/projects/python-markdown/repos/mainline/

Note that with git you don't need commit privileges to play - you can
just "clone" a repository (essentially make a branch), and commit into
it.  We can then merge from it later.

  - yuri

-- 
http://sputnik.freewisdom.org/

[Python-markdown-discuss] mdx_tables bug

[glin <gl...@se...>]

Hi,

on your wiki you have extension mdx_tables 
(http://www.freewisdom.org/projects/python-markdown/mdx_tables).

When I use some inline mark (like *something*, link etc.) in table cell, 
the cell content renders in reverse order. And I can use only one inline 
mark (others are not taken in account).

IMHO this extension shouldn't use _handleInline method, but 
_handleInlineWrapper2. I went through the source code of markdown and it 
appears, that _handleInline is only some 'private' function used by 
_handleInlineWrapper2 - so _handleInline applies only one pattern and 
returns chunks in reverse order, which is completely wrong and will do 
mess when you use any inline pattern in table.

So I think, that you should replace:

			for n in self.md._handleInline(t):
				if(type(n) == unicode):
					td.appendChild(doc.createTextNode(n))
				else:
					td.appendChild(n)

with:

			for item in self.md._handleInlineWrapper2(t) :
				td.appendChild(item)

I don't have permission to wiki so I cannot write it there, so I'm 
sending this email to mailinglist.

Glin

Re: [Python-markdown-discuss] Markdown extras?

[Jan E. M. <li...@mo...>]

Waylan Limberg <wa...@gm...> 08-04-25 09.58

>Definition lists are something I'd like to see added, but I've been
>too busy with other stuff. If you want to give it a try, I'd be
>willing to offer some help.

I'll have to take a look and see if I can figure out something 
(no promises, my schedule seem to break down regularly ... at 
least twice a day).

Yuri Takhteyev <qar...@gm...> 08-04-28 12.06

>since Markdown syntax is already fragmented enough...

I agree on that, I've been a "plain markdown" person since 
markdown was first released ... but I recently switched to 
multimarkdown since it better covers my needs.

                             jem
-- 
Jan Erik Moström, www.mostrom.pp.se

Re: [Python-markdown-discuss] Markdown extras?

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

I don't think this is supported in any of the extensions that I am
aware of.   If it were added, it would need to be an extension at this
point, since Markdown syntax is already fragmented enough...

  - yuri

On Fri, Apr 25, 2008 at 6:58 AM, Waylan Limberg <wa...@gm...> wrote:
> Hi Jan,
>
>  I know definition lists have come up on this list a few times, but I'm
>  not currently aware of a working implementation. A list of all the
>  publicly available extensions I know of can be found here [1].
>  Definition lists are something I'd like to see added, but I've been
>  too busy with other stuff. If you want to give it a try, I'd be
>  willing to offer some help.
>
>  [1]: http://www.freewisdom.org/projects/python-markdown/Available_Extensions
>
>
>
>  On Fri, Apr 25, 2008 at 1:54 AM, Jan Erik Moström <li...@mo...> wrote:
>  > Hi,
>  >
>  >  I haven't been following the Python version that closely the
>  >  last year so I would like to ask if there is a version that
>  >  supports definition lists? (actually I would like to see
>  >  something like multimarkdown but defintion lists are enough for
>  >  what I've got in mind)
>  >  --
>  >  Jan Erik Moström, www.mostrom.pp.se
>  >
>  >
>  >  -------------------------------------------------------------------------
>  >  This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>  >  Don't miss this year's exciting event. There's still time to save $100.
>  >  Use priority code J8TL2D2.
>  >  http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>  >  _______________________________________________
>  >  Python-markdown-discuss mailing list
>  >  Pyt...@li...
>  >  https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>  >
>
>
>
>  --
>  ----
>  Waylan Limberg
>  wa...@gm...
>
>
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>  Don't miss this year's exciting event. There's still time to save $100.
>  Use priority code J8TL2D2.
>  http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>  _______________________________________________
>  Python-markdown-discuss mailing list
>  Pyt...@li...
>  https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



-- 
http://sputnik.freewisdom.org/

Re: [Python-markdown-discuss] code moved to gitorious

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

>  You need to specify a repository to pull from gitorious, which is called
>  "mainline" for the default branch.

Also, it's "gitorious" with an "O" between "i" and "u".  To rhyme with
"glorious", I assume.

>     git clone git://gitorious.org/python-markdown/mainline.git

Yes, this command works.

 - yuri

-- 
http://sputnik.freewisdom.org/

Re: [Python-markdown-discuss] code moved to gitorious

[Jeff B. <its...@gm...>]

Waylan Limberg wrote:
> On Sun, Apr 27, 2008 at 3:14 AM, Yuri Takhteyev <qar...@gm...> wrote:
> > I converted the source repository to git and moved it to
> >  gitorious.org: http://gitorious.org/projects/python-markdown
> >
> 
> Cool! But, I can't seem to be able to get it. I've tried both git//:
> and http//: schemes:
> 
>     waylan@desktop:~/code$ git clone git://gitorius.org/python-markdown
>     Initialized empty Git repository in /home/waylan/code/python-markdown/.git/
>     fatal: unable to connect a socket (Connection timed out)
>     fetch-pack from 'git://gitorius.org/python-markdown' failed.
>     waylan@desktop:~/code$ git clone http://git.gitorius.org/python-markdown
>     Initialized empty Git repository in /home/waylan/code/python-markdown/.git/
>     Cannot get remote repository information.
>     Perhaps git-update-server-info needs to be run there?
> 

You need to specify a repository to pull from gitorious, which is called
"mainline" for the default branch.

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

    You can clone this repository with the following command:
    git clone git://gitorious.org/python-markdown/mainline.git

Re: [Python-markdown-discuss] code moved to gitorious

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

On Sun, Apr 27, 2008 at 3:14 AM, Yuri Takhteyev <qar...@gm...> wrote:
> I converted the source repository to git and moved it to
>  gitorious.org: http://gitorious.org/projects/python-markdown
>

Cool! But, I can't seem to be able to get it. I've tried both git//:
and http//: schemes:

    waylan@desktop:~/code$ git clone git://gitorius.org/python-markdown
    Initialized empty Git repository in /home/waylan/code/python-markdown/.git/
    fatal: unable to connect a socket (Connection timed out)
    fetch-pack from 'git://gitorius.org/python-markdown' failed.
    waylan@desktop:~/code$ git clone http://git.gitorius.org/python-markdown
    Initialized empty Git repository in /home/waylan/code/python-markdown/.git/
    Cannot get remote repository information.
    Perhaps git-update-server-info needs to be run there?



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

[Python-markdown-discuss] code moved to gitorious

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

I converted the source repository to git and moved it to
gitorious.org: http://gitorious.org/projects/python-markdown

This change should give us the many advantages of git, a more sensible
browsing interface, plus the ability tof maintain several linked
repositories with different owners.  If you want to make a branch, you
don't not need to ask for my permission: just make an account on
gitorious, clone the repository and start hacking.  If you later think
you have something that we should merge into the main repository, just
email the list and I or Waylan will merge it.  (And if for some reason
we don't, your repository will still exist side by side with the
"official" one and people can draw on it if they prefer.)

 - yuri

-- 
http://sputnik.freewisdom.org/

Re: [Python-markdown-discuss] Markdown extras?

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

Hi Jan,

I know definition lists have come up on this list a few times, but I'm
not currently aware of a working implementation. A list of all the
publicly available extensions I know of can be found here [1].
Definition lists are something I'd like to see added, but I've been
too busy with other stuff. If you want to give it a try, I'd be
willing to offer some help.

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

On Fri, Apr 25, 2008 at 1:54 AM, Jan Erik Moström <li...@mo...> wrote:
> Hi,
>
>  I haven't been following the Python version that closely the
>  last year so I would like to ask if there is a version that
>  supports definition lists? (actually I would like to see
>  something like multimarkdown but defintion lists are enough for
>  what I've got in mind)
>  --
>  Jan Erik Moström, www.mostrom.pp.se
>
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>  Don't miss this year's exciting event. There's still time to save $100.
>  Use priority code J8TL2D2.
>  http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>  _______________________________________________
>  Python-markdown-discuss mailing list
>  Pyt...@li...
>  https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



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

[Python-markdown-discuss] Markdown extras?

[Jan E. M. <li...@mo...>]

Hi,

I haven't been following the Python version that closely the 
last year so I would like to ask if there is a version that 
supports definition lists? (actually I would like to see 
something like multimarkdown but defintion lists are enough for 
what I've got in mind)
-- 
Jan Erik Moström, www.mostrom.pp.se

Re: [Python-markdown-discuss] Google Summer of Code

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

Congratulations, Artem!  I am looking forward to your participation.

This will be the first GSoC experience for the project, as well as for
myself personally, but we'll do our best!

  - yuri

On Tue, Apr 22, 2008 at 8:47 AM, Waylan Limberg <wa...@gm...> wrote:

> Welcome Artem.
>
> On Tue, Apr 22, 2008 at 10:48 AM, Artem <ne...@gm...> wrote:
> > Hello, my name is Artem Yunusov, I'm a 4th-year student of Izhevsk State
> >  Technical University. I'll be working on markdown module within Google
> >  Summer of Code 2008 program. Information about the application can be
> >  found here
> >  http://code.google.com/soc/2008/psf/appinfo.html?csaid=629D6DD6AB59F359
> >  This is the first time I've participated in the GSoC.
> >  Best regards!
>


-- 
http://sputnik.freewisdom.org/

Re: [Python-markdown-discuss] Google Summer of Code

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

Welcome Artem.

On Tue, Apr 22, 2008 at 10:48 AM, Artem <ne...@gm...> wrote:
> Hello, my name is Artem Yunusov, I'm a 4th-year student of Izhevsk State
>  Technical University. I'll be working on markdown module within Google
>  Summer of Code 2008 program. Information about the application can be
>  found here
>  http://code.google.com/soc/2008/psf/appinfo.html?csaid=629D6DD6AB59F359
>  This is the first time I've participated in the GSoC.
>  Best regards!
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>  Don't miss this year's exciting event. There's still time to save $100.
>  Use priority code J8TL2D2.
>  http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>  _______________________________________________
>  Python-markdown-discuss mailing list
>  Pyt...@li...
>  https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



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

Re: [Python-markdown-discuss] Google Summer of Code

[David W. <wo...@cs...>]

Hurra!

On 22-Apr-08, at 10:48 AM, Artem wrote:
> Hello, my name is Artem Yunusov, I'm a 4th-year student of Izhevsk  
> State
> Technical University. I'll be working on markdown module within Google
> Summer of Code 2008 program. Information about the application can be
> found here
> http://code.google.com/soc/2008/psf/appinfo.html? 
> csaid=629D6DD6AB59F359
> This is the first time I've participated in the GSoC.
> Best regards!
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save  
> $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http:// 
> java.sun.com/javaone
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss

[Python-markdown-discuss] Google Summer of Code

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

Hello, my name is Artem Yunusov, I'm a 4th-year student of Izhevsk State 
Technical University. I'll be working on markdown module within Google 
Summer of Code 2008 program. Information about the application can be 
found here 
http://code.google.com/soc/2008/psf/appinfo.html?csaid=629D6DD6AB59F359
This is the first time I've participated in the GSoC.
Best regards!

Re: [Python-markdown-discuss] git and gitorious

[David W. <wo...@cs...>]

I certainly wouldn't complain about moving to a DVCS :)

Now, if I had my way, it would be bzr+Launchpad... But, since I don't  
want my way badly enough to orchestrate any sort of large-scale  
changes, I won't complain too loudly ;)

On 24-Mar-08, at 8:36 PM, Yuri Takhteyev wrote:

> Waylan's patch reminded me of something I wanted to bring up:  
> should we consider moving from SF's subversion to something a tiny  
> little bit less sucky?  I recently moved Sputnik over to a git  
> repository hosted by gitorious.org and I since can't stop telling  
> people how much in love I am with both git and gitorious.  I wake  
> up in the morning and look forward to the day knowing that if  
> someone emails me a patch it will be in form of a link to something  
> like:
>
> http://gitorious.org/projects/sputnik/repos/mainline/commits/ 
> 3028915518ebdc0574bf3255f2ffa48c82e395eb
>
> And that it would then take me no time to integrate it, even if my  
> own code has moved on.
>
> There is also a nice open-sourcy thing about gitorious (and git  
> more generally), in that people don't need my permission to start  
> making clones and commits (into their clones).  They just need to  
> email me a list of commits later.  Click around the Sputnik  
> gitorious repository and compare this with what we have now:
>
> Gitorious: http://gitorious.org/projects/sputnik/
> SF:  http://python-markdown.svn.sourceforge.net/viewvc/python- 
> markdown/
>
>  - yuri
>
> -- 
> http://sputnik.freewisdom.org/
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ 
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss