Source code inlines

[Upabjojr]

Shall we use some proper libraries instead of \begin{verbatim} ... \end{verbatim} for source code inlining?

https://en.wikibooks.org/wiki/LaTeX/Source_Code_Listings

[leosartaj]

I used minted for my gsoc proposal. It worked well for me.

[moorepants]

I've included minted in PR #38. If we merge it, it is available and runs on travis.

[moorepants]

We also need to make sure that all use the same format (python prompt, ipython prompt, no prompt?), as per discussion in #50 .

[sumith1896]

So what's the stand on this (python prompt, ipython prompt, no prompt?) ?

We can make all the code as of now uniform.

[moorepants]

If you want to show input and output we should use a prompt. I don't care if it is the python or ipython prompt.

If you are going to go through and change things, can you change them all to use minted so that we get nice syntax highlighting?

[sumith1896]

@moorepants We need to figure this out too https://github.com/sympy/sympy-paper/issues/9 , the point about computational reproducibility as even this is pertaining to the examples. Once, we have both sorted out we can fix all the examples in one go.

[certik]

I think using the Python prompt >>> might be easier to get (later) working with a doctest style testing. So let's use >>> for now?

[asmeurer]

My vote is for the python prompt, and the default (str) printing. We should also state at the beginning of the paper that all examples are run with from sympy import *.