From: Ivan M. <ph...@gm...> - 2013-03-24 12:49:54
|
OK, I understand how this is out of scope for the project. I'll look into your suggestions. Thanks guys, Ivan On Sun, Mar 24, 2013 at 2:48 AM, Waylan Limberg <wa...@gm...> wrote: > Ivan, > > This is way out of scope for Markdown. That said, I don't see why an > extension wouldn't be able to do something like that. I don't really > recommend this approach, but I suppose an inline pattern would do the > trick. > > Another approach, and one I know some have used successfully, is to > pass the markdown text through a template system first (like Jinja) - > which replaces the variables - then pass it through the markdown > parser. Or maybe they passed it through markdown first, then the > template system. I'm sure one or the other could work depending upon > the needs of the specific project. Personally, this would be my > approach - rather than an extension to markdown. > > > On Sat, Mar 23, 2013 at 6:34 PM, Ivan Mirić <ph...@gm...> wrote: > > Hi, > > > > Is there a chance of adding the ability to access Python variables from > > Markdown? > > > > As seen here (https://github.com/ipython/ipython/issues/2958), the > `{{}}` > > syntax would be great. > > > > If this is not in the pipeline as a built-in Python-Markdown feature, how > > difficult would it be to write an extension for it? If someone points me > in > > the right direction, I might attempt it myself. > > > > Thanks, > > > > Ivan > > > > > ------------------------------------------------------------------------------ > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics > > Download AppDynamics Lite for free today: > > http://p.sf.net/sfu/appdyn_d2d_mar > > _______________________________________________ > > Python-markdown-discuss mailing list > > Pyt...@li... > > https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss > > > > > > -- > ---- > \X/ /-\ `/ |_ /-\ |\| > Waylan Limberg > |