-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Traceback appears twice in v0.14 #70
Comments
I can't reproduce the problem. You might try deleting the Are you loading any packages besides |
Deleting \documentclass[pdftex]{article}
\usepackage{pythontex}
\begin{document}
\begin{frame}[fragile]
\begin{pyconsole}
raise Exception
\end{pyconsole}
\end{frame}
\end{document} |
In the directory with the main |
The
The only files that differ significantly are the v0.12:
v0.14:
|
Can you give me your complete Python version, so I can check that on my system? I think I'm getting closer on diagnosing the issue. Under Ubuntu 14.04, Python 2.7.6 gives correct output but Python 3.4.0 is completely omitting all traceback information. The traceback is ending up in the terminal instead. Under Windows, everything works fine for Python 3.4.1. My guess is that Python 3 treats the emulated console stdout and stderr differently on some systems, so that it is being doubled (your case) or ending up in the wrong place (my Ubuntu case). I will need to look into how Python's |
I'm running Python 3.4.2 on a Debian Jessie. The samples I provided for v0.12 (the correct ones) use Python 3.2.3 on a Debian Wheezy, so there might have been changes between those two versions. |
I believe I've found the issue and a solution. Apparently Ubuntu's |
I use a pyconsole in a latex-beamer frame, with an expression leading to an error. For example:
This compiles fine with pythontex3 v0.12, but produces a double backtrace with v0.14:
I'm on Debian Jessie, and the package is simply loaded with
\usepackage{pythontex}
.The text was updated successfully, but these errors were encountered: