%<latex>\ProvidesPackage{sagetex}

%<python>__version__ = """

- [2009/~~07/27~~ v2.2.3 embedding Sage into LaTeX documents]

+ [2009/12/30 v2.2.3 embedding Sage into LaTeX documents]

% filename, including it into your document, and so on. In

% \autoref{sec:usage}, we will see what what we can do with \ST.

% \label{sec:installation}

% \changes{v2.0}{2009/01/14}{Fixed up installation section, final

% \newcommand{\sageroot}{\$SAGE\_ROOT}

-% new installation section FIXME FIXME FIXME

-% \ST needs two parts to work: a Python module known to Sage, and a

-% \LTX package known to \TeX. As of Sage version 4.3.1, \ST comes

-% included with Sage, so you only need to make sagetex.sty, the \LTX

-% package, known to \TeX. Full details of this are in the Sage

-% Installation guide at http://sagemath.org/doc/installation/ in the

-% obviously-named section ``Make \ST known to \TeX''. Here's a brief

-% summary of how to do that:

+% \ST needs two parts to work: a Python module known to Sage, and a \LTX

+% package known to \TeX. These two parts need to come from the same

+% version of \ST to guarantee that everything works properly. As of Sage

+% version 4.3.1, \ST comes included with Sage, so you only need to make

+% \texttt{sagetex.sty}, the \LTX package, known to \TeX. Full details of

+% this are in the Sage Installation guide at

+% \href{http://sagemath.org/doc/installation/}{\texttt{sagemath.org/doc/installation/}}

+% in the obviously-named section ``Make \ST known to \TeX''. Here's a

+% brief summary of how to do that:

+% \item Copy \texttt{sagetex.sty} to the same directory as your

+% document. This always works, but requires lots of copies of

+% \texttt{sagetex.sty} and is prone to version skew.

-% \item Copy sagetex.sty to the same directory as your document. This

-% always works, but requires lots of copies off sagetex.sty and is prone

+% \item Use the environment variable \texttt{TEXINPUTS} to tell \TeX{}

+% to search the directory containing \texttt{sagetex.sty}; in the bash

+% \texttt{export TEXINPUTS=\sageroot/local/share/texmf//:}

+% You should replace \texttt{\sageroot} with the location of your Sage

-% \item Set the environment variable TEXINPUTS to

-% ``\sageroot/local/share/texmf//:'', where \sageroot refers to the

-% location of your Sage install.

-% \item Copy the above directory to your home directory with a command

-% like ``cp -R \sageroot/local/share/texmf ~/''.

+% \item Copy the directory containing \texttt{sagetex.sty} to your home

+% directory with a command like

+% \texttt{cp -R \sageroot/local/share/texmf \textasciitilde/}

+% where again you replace \texttt{\sageroot} with the location of your

-% I prefer using TEXINPUTS, as it guarantees that both Sage and \TeX are

-% using synchronized code.

+% I prefer using \texttt{TEXINPUTS}, as it guarantees that both Sage and

+% \TeX{} are synchronized and doesn't require you to copy any files.

+% Note that along with \texttt{sagetex.sty}, this documentation, an

+% example file, and other useful scripts are all located in the

+% directory \texttt{\sageroot/local/share/texmf}.

% \subsection{\ST and \TeX Live}

% the \LTX package from \TeX Live and the Python module from Sage, they

% may not work together if they are from different versions of \ST.

% Because of this, I strongly recommend using \ST only from what is

-% included with Sage and ignoring what's included with \TeX Live.~~ ~~

+% included with Sage and ignoring what's included with \TeX Live.

% \subsection{Using \TeX Shop}

% \label{sec:using-texshop}

% at the top of your document, then \TeX Shop will automatically run Sage

% for you when compiling your document.

-% Note that you will need to make |sagetex.sty| and |sagetex.py| known

-% to \LTX and Sage using any of the methods described above (although

-% note that \TeX Shop includes copies of these files for you). You also

-% might need to edit the |sage.engine| script to reflect the location of

-% your Sage installation.

+% Note that you will need to make sure that \LTX can find |sagetex.sty|

+% using any of the methods above. You also might need to edit the

+% |sage.engine| script to reflect the location of your Sage

% \subsection{Other scripts included with \ST}

% \label{sec:inst-other-scripts}