[SciPy-Dev] Migrating to Markdown Syntax from reStructured Text in SPC

Andreas Hilboll lists@hilboll...
Thu Jul 4 04:29:50 CDT 2013


On 04.07.2013 11:23, Matthias BUSSONNIER wrote:
> Hi all, 
> 
> Le 4 juil. 2013 à 10:30, Surya Kasturi a écrit :
> 
>> 1. reST has some security issues - Someone can put some raw HTML in it
>> and thus creating vulnerabilities.. Better explained at
>>
>> https://docs.djangoproject.com/en/1.4/ref/contrib/markup/#restructured-text
> 
> But markdown is a superset of HTML… so you implicitly allow to write
> html if you switch to MD… but you can sanitize.. (just sayin')
> 
>> 2. currently reST to HTML conversion is done on the server side! It
>> could be done on client side enabling better text editing and
>> previewing..
> 
> I hope you cache the redered pages…
> 
>> Markdown seems to be a decent option since there are some opensource
>> tools (by Stackoverflow) and we can start integrating them with our site
>>
>> http://code.google.com/p/pagedown/wiki/PageDown
>> (link previously referred by Sebastian during discussion - thanks!)
> 
> IPython just switched from PageDown to Marked… it support GFM, and user
> are really used to it. 
> 
> 
> Le 4 juil. 2013 à 10:38, Andreas Hilboll a écrit :
> 
>> On 04.07.2013 10:30, Surya Kasturi wrote:
> 
>> Using markdown might also make the notebook export easier, right?
> 
> That's funny, a few weeks ago we were saying that markdown was too
> restrictive and that
> it might be worth fixing rst problem than trying to extend markdown and
> switching back to 
> rst one day… (don't worry, not soon), discussion should have been
> recored on youtube.

Well, I personally do prefer reST. So if the reST problems were fixed
and the notebooks would support reST, then reST would be my favourite
SPyCe solution ... But until then, using MD in SPyCe would make the
notebook export easier.

-- Andreas.



More information about the SciPy-Dev mailing list