python-markdown-discuss

[Python-markdown-discuss] breaking up into multiple files

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

Now that we have all the logic broken up, it's a shame to have it all
in a single giant file.  Here is an attempt at refactoring:

http://gitorious.org/projects/python-markdown/repos/mainline/logs/repackaging

What do you think?

Note that the command line markdown.py still works as long as the
"markdown" directory is either in the path.  I didn't break things up
all the way yet.  We should be able to reduce the core file to about
500 lines or less.

  - yuri

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

Re: [Python-markdown-discuss] breaking up into multiple files

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

On Mon, Nov 17, 2008 at 3:27 AM, Yuri Takhteyev <qar...@gm...> wrote:
> Now that we have all the logic broken up, it's a shame to have it all
> in a single giant file.  Here is an attempt at refactoring:
>
> http://gitorious.org/projects/python-markdown/repos/mainline/logs/repackaging
>
> What do you think?

I've wanted to do this for some time. I like it! It also means we can
put the extensions at ``markdown.extensions.footnotes``, rather than
``markdown_extensions.footnotes``. Much better IMO.

>
> Note that the command line markdown.py still works as long as the
> "markdown" directory is either in the path.

Cool!

> I didn't break things up all the way yet.

It looks like `postprocessors`, `util`, and maybe `etree` are left to do.

I noticed you went with `linepreprocessors`. As there are only one
kind of preprocessors, why not just `preprocessors`?



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