Re: [Python-markdown-discuss] Also Deprecating mdx_* extension names?

[Dave P. <dav...@gm...>]

No objection to either proposal. Uniformity and extensibility are good.

Is there an 'ideas bucket' for future changes please?

regards Dave P

On 22 August 2014 21:28, Waylan Limberg <way...@ic...> wrote:
> While we're talking about deprecating things related to extensions, I would
> like to deprecate support for the `mdx_*` naming convention of third party
> extensions. I updated the docs [over a year ago][1] suggesting that this
> might happen. As we support passing in instances of extension classes and
> strings using dot notation, I don't see any reason to keep this around
> except that some existing third party exceptions still use it. Although, the
> ones that do appear to not be regularly maintained which suggests they are
> not too popular.
>
> Any objections?
>
> And while I have your attention, I have also considered deprecating the
> special treatment of the included extensions. In order words, one would need
> to do `extensions=['markdown.extensions.extra']` (which has worked for some
> time, btw) rather than `extensions=['extra']. However, I feel less strongly
> about this and I realize that this would require almost all our users to
> change their code upon updating. Perhaps it would be sufficient to change
> the docs so that any mention of the special treatment  is omitted (the docs
> would suggest that all 'named extensions' would use dot notation). Any
> thoughts?
>
> Waylan Limberg
>
>
> [1]:
> https://github.com/waylan/Python-Markdown/commit/8aa2fc7b5138fd97ded7dd1e70103532a9fd6583
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk