Source code inlines about sympy-paper HOT 8 OPEN

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

from sympy-paper.

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

from sympy-paper.

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

from sympy-paper.

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

We can make all the code as of now uniform.

from sympy-paper.

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?

from sympy-paper.

@moorepants We need to figure this out too #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.

from sympy-paper.

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

from sympy-paper.

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

from sympy-paper.