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/