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...