Specifying executable code chunk in LaTeX with 'exec' inside lstlisting environment causes compilation error

[fkmendes]

Currently, executable code chunks in LaTeX are specified like this:

\begin{lstlisting}[language=Python, exec]
# some executable Python code
\end{listing}

this cannot be compiled by LaTeX, however. Here's a possible solution:

% start exec
\begin{lstlisting}[language=Python, exec]
# some executable Python code
\end{listing}
% end exec

Having a start and end string makes parsing easy.
Note that % marks commented for LaTeX (so it doesn't cause compilation errors).

[nokome]

Thanks @fkmendes . How about % begin instead of % start to be consistent with LaTeX? Also we drop the exec as an option, so...

% begin exec
\begin{lstlisting}[language=Python]
# some executable Python code
\end{lstlisting}
% end exec

Right?

[nokome]

How would we deal with inline CodeExpressions? The current syntax is An evaluated Python expression \lstinline[language=python exec]{pow(2,2)}.. I feel that we should check to see if alternative language specifications e.g. python-exec are valid before looking for alternatives.