python-markdown-discuss

[Python-markdown-discuss] Proposed File Cleanup and reorg.

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

I just created a new branch [1] that reorganizes and (IMO) cleans up
the file system a little. All the text files are moved into a 'docs/'
dir and all the extensions have been moved into a 'mdx/' dir. It feels
so much less cluttered to me this way.

I should note that, as you can see in this commit [2], it still tries
the old way of importing the 'mdx_extname.py' first, then on failure,
'mdx.mdx_extname.py'. That way, people can create their own
extensions, give it the same name, put it on their PYTHONPATH and it
will override the distributed extension - all without them needing to
modify the distributed code. Thus, in any future upgrades, their work
won't get overwritten. Plus, those who don't actually install, but
have everything in the working dir still get the current behavior if
they want.

Anyone have any objections to either the docs or extensions move? If
there's no objections, I'll merge it in. If I get objections to only
one or the other, I can work with that too.

One other question: if we do the extension reorg, should the
extensions be 'mdx.mdx_extname.py' or 'mdx.extname.py'? It's just that
the extra 'mdx' seems redundant - but given that we've already
established that naming convention, maybe we should leave it.
Thoughts?

Oh, I added AUTHORS and INSTALL files in the docs. The INSTALL file is
vary incomplete and those sections of the README should probably be
removed.

[1]: http://gitorious.org/projects/python-markdown/repos/mainline/trees/reorg
[2]: http://gitorious.org/projects/python-markdown/repos/mainline/commits/2b7e391fcd51d3468133f628f2e013574cf16536#markdown.py
-- 
----
Waylan Limberg
wa...@gm...

Re: [Python-markdown-discuss] Proposed File Cleanup and reorg.

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

Waylan Limberg wrote:
> Anyone have any objections to either the docs or extensions move? If
> there's no objections, I'll merge it in. If I get objections to only
> one or the other, I can work with that too.
>   

I don't have any objections, and think it's good idea.
> One other question: if we do the extension reorg, should the
> extensions be 'mdx.mdx_extname.py' or 'mdx.extname.py'? It's just that
> the extra 'mdx' seems redundant - but given that we've already
> established that naming convention, maybe we should leave it.
> Thoughts?
>   

Vote for names without "mdx_" prefix :) we already have namespace for 
extension and there is no need to add pseudo-namespace. I think in 
general, such technique(adding prefixes) is unpythonic, because in 
Python we have real namespacing.

Re: [Python-markdown-discuss] Proposed File Cleanup and reorg.

[Yuri T. <yu...@si...>]

I like the re-org overall.   Just a few suggestions.

First, let's move the extensions to a separate directory as Waylan
did, but let's give it a more explicit name, now that we are at it.
How about putting them in markdown/extensions, and then importing them
as markdown.extensions.foo?

Second, let's get rid of the "mdx_" prefices for modules that will be
moved into a package, but let's keep support for the old style mdx_*
extensions (unpackaged).  Let's make this a fallback, thought.  I.e.,
if someone wants to use "foo" extension, _first_ try to load
markdown.extensions.foo, and if this doesn't work, check "mdx_foo".

 - yuri

On Sun, Aug 10, 2008 at 2:40 PM, Artem Yunusov <ne...@gm...> wrote:
> Waylan Limberg wrote:
>> Anyone have any objections to either the docs or extensions move? If
>> there's no objections, I'll merge it in. If I get objections to only
>> one or the other, I can work with that too.
>>
>
> I don't have any objections, and think it's good idea.
>> One other question: if we do the extension reorg, should the
>> extensions be 'mdx.mdx_extname.py' or 'mdx.extname.py'? It's just that
>> the extra 'mdx' seems redundant - but given that we've already
>> established that naming convention, maybe we should leave it.
>> Thoughts?
>>
>
> Vote for names without "mdx_" prefix :) we already have namespace for
> extension and there is no need to add pseudo-namespace. I think in
> general, such technique(adding prefixes) is unpythonic, because in
> Python we have real namespacing.
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



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

Re: [Python-markdown-discuss] Proposed File Cleanup and reorg.

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

On Mon, Aug 11, 2008 at 4:31 PM, Yuri Takhteyev <yu...@si...> wrote:
> I like the re-org overall.   Just a few suggestions.
>
> First, let's move the extensions to a separate directory as Waylan
> did, but let's give it a more explicit name, now that we are at it.
> How about putting them in markdown/extensions, and then importing them
> as markdown.extensions.foo?

Unless I'm missing something, we can't do this unless we make markdown
a package. At the least we'd have to put the contents of markdown.py
in markdown/__init__.py which completely removes any usefulness of
markdown.py as a commandline script. I suppose we could do
markdown/markdown.py and then have markdown/__init__.py just do a
``import *``

>
> Second, let's get rid of the "mdx_" prefices for modules that will be
> moved into a package, but let's keep support for the old style mdx_*
> extensions (unpackaged).  Let's make this a fallback, thought.  I.e.,
> if someone wants to use "foo" extension, _first_ try to load
> markdown.extensions.foo, and if this doesn't work, check "mdx_foo".

No problem, I can do it that way too.

>
>  - yuri
>
> On Sun, Aug 10, 2008 at 2:40 PM, Artem Yunusov <ne...@gm...> wrote:
>> Waylan Limberg wrote:
>>> Anyone have any objections to either the docs or extensions move? If
>>> there's no objections, I'll merge it in. If I get objections to only
>>> one or the other, I can work with that too.
>>>
>>
>> I don't have any objections, and think it's good idea.
>>> One other question: if we do the extension reorg, should the
>>> extensions be 'mdx.mdx_extname.py' or 'mdx.extname.py'? It's just that
>>> the extra 'mdx' seems redundant - but given that we've already
>>> established that naming convention, maybe we should leave it.
>>> Thoughts?
>>>
>>
>> Vote for names without "mdx_" prefix :) we already have namespace for
>> extension and there is no need to add pseudo-namespace. I think in
>> general, such technique(adding prefixes) is unpythonic, because in
>> Python we have real namespacing.
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>> Build the coolest Linux based applications with Moblin SDK & win great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Python-markdown-discuss mailing list
>> Pyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>>
>
>
>
> --
> http://sputnik.freewisdom.org/
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



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

Re: [Python-markdown-discuss] Proposed File Cleanup and reorg.

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

> Unless I'm missing something, we can't do this unless we make markdown
> a package. At the least we'd have to put the contents of markdown.py
> in markdown/__init__.py which completely removes any usefulness of
> markdown.py as a commandline script. I suppose we could do
> markdown/markdown.py and then have markdown/__init__.py just do a
> ``import *``

Right... I am forgetting that Python is not Lua and you can't have it
both ways. :)

No, let's not turn markdown into a package.  Let's call the extension
package something else, but something explicit.  Perhaps
"markdown_extensions"?

 - yuri

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

Re: [Python-markdown-discuss] Proposed File Cleanup and reorg.

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

> Unless I'm missing something, we can't do this unless we make markdown
> a package. At the least we'd have to put the contents of markdown.py
> in markdown/__init__.py which completely removes any usefulness of
> markdown.py as a commandline script. I suppose we could do
> markdown/markdown.py and then have markdown/__init__.py just do a
> ``import *``

Right... I am forgetting that Python is not Lua and you can't have it
both ways. :)

No, let's not turn markdown into a package.  Let's call the extension
package something else, but something explicit.  Perhaps
"markdown_extensions"?

 - yuri

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

Re: [Python-markdown-discuss] Proposed File Cleanup and reorg.

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

> Unless I'm missing something, we can't do this unless we make markdown
> a package. At the least we'd have to put the contents of markdown.py
> in markdown/__init__.py which completely removes any usefulness of
> markdown.py as a commandline script. I suppose we could do
> markdown/markdown.py and then have markdown/__init__.py just do a
> ``import *``

Right... I am forgetting that Python is not Lua and you can't have it
both ways. :)

No, let's not turn markdown into a package.  Let's call the extension
package something else, but something explicit.  Perhaps
"markdown_extensions"?

 - yuri

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

Re: [Python-markdown-discuss] Proposed File Cleanup and reorg.

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

In case anyone is wondering, the reason for the triple message is
gmail downtime...  They tell you they couldn't send the message even
though they did...

  - yuri

On Mon, Aug 11, 2008 at 2:58 PM, Yuri Takhteyev <qar...@gm...> wrote:
>> Unless I'm missing something, we can't do this unless we make markdown

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

Re: [Python-markdown-discuss] Proposed File Cleanup and reorg.

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

Yeah, well I couldn't access my gmail account so I didn't know you
sent three copies.

Anyway, I made the adjustments you suggested and merged. I just pushed
the changes. If anyone has any problems please let me know.

On Mon, Aug 11, 2008 at 7:07 PM, Yuri Takhteyev <qar...@gm...> wrote:
> In case anyone is wondering, the reason for the triple message is
> gmail downtime...  They tell you they couldn't send the message even
> though they did...
>
>  - yuri
>
> On Mon, Aug 11, 2008 at 2:58 PM, Yuri Takhteyev <qar...@gm...> wrote:
>>> Unless I'm missing something, we can't do this unless we make markdown
>
> --
> http://sputnik.freewisdom.org/
>



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