index error when code error

[obtitus]

I get the following error when I type something wrong in the pylabcode environment:
while not codefile[errlinenumber].startswith('pytex.inputline=') and errlinenumber>-1:
IndexError: list index out of range

[gpoore]

I just pushed an updated version that will fix the IndexError. This was caused by the error message parser trying to read beyond the beginning of the error file. Since pythontex.py was trying to parse an error message (unsuccessfully), your code is apparently producing some type of error that it cannot connect with a specific line number. I would be very interested in an example, if you can post one, so I can refine error handling.

[obtitus]

Good, the error is caused by calling an external function (so no latex line number) with the wrong argument. I can post a minimal example if you wish.

[gpoore]

I would be interested in a minimal example.

[obtitus]

On May 10, 2012, at 2:52 , gpoore wrote:

I would be interested in a minimal example.

---

Reply to this email directly or view it on GitHub:
#1 (comment)

\documentclass{article}
\usepackage{pythontex}
\begin{document}
Hello world
\begin{pylabcode}
x = linspace(0, 2*pi)
plot(x, sin(x))
savefig('pic/sin.pdf') # fails since pythontex-files-myTest/pic/ does not exist
\end{pylabcode}
\end{document}

produces:
This is PythonTeX v0.9beta
Hashing...
Parsing...
Executing...
Cleaning up and reporting errors...

Errors for pylab_default_default
Traceback (most recent call last):

• PythonTeX code error on line 13:
  File "pythontex-files-myTest/pylab_default_default.py", line 26, in
  savefig('pic/sin.pdf')
  Traceback (most recent call last):
  File "/Users/ob/bin/pythontex.py", line 699, in
  while not codefile[errlinenumber].startswith('pytex.inputline=') and errlinenumber>-1:
  IndexError: list index out of range

The above code is fixed by using
savefig('../pic/sin.pdf')

Another issue: it would be prefferable if user code is run in the root directory so that the original example would work. Regards,

Øystein Bjørndal

[gpoore]

Thanks for the example. It turns out that the previous fix didn't actually resolve the issue. I fixed the actual cause: e064b10

[gpoore]

Code currently runs in the pythontex-files-{jobname} directory so as to isolate all PythonTeX-generated content. But I can see why it might be useful to be able to run in a user-specified directory. I will look into adding that as a feature in the next commit.

By the way, any graphics created in pythontex-files-{jobname} are available without specifying the directory if you are using the package graphicx. For example, if you create sin.pdf in pythontex-files-myTest, you can access it via \includegraphics{sin.pdf}, without specifying the directory. This behavior is set automatically via \graphicspath. But it hasn't yet made it into the non-technical part of the documentation.

[gpoore]

Regarding the directory in which code runs: Beta 3 addresses this, with the \setpythontexworkingdir macro.