Ernst Reissner
Ernst Reissner
From the documentation, Section 3.2 we read: > --error-exit-code={true,false} By default, pythontex.py returns an > exit code of 1 if there were any errors, and an exit code of 0...
In all but 2 cases the messages of errors are signified by the message text ``` * PythonTeX error ``` In lines 219 and 370, this is not the case....
For the error Could not find external file on line 2422 in the python3 script of pythontex the error counter is seemingly not incremented. Is this a bug?
I think, it should be sth like rerun=missing: rerun is triggered, if an expected output file is missing.
Does a non fatal error yield error code 1 by default? Not to say when asking pythontex --help.
In the package documentation Section 4.1 it seems as if there is a slight difference between rerun=always and runall=true. At least the formulations are different. I found out that the...
According to the documentation, when concurrent package options and command line options, always package options are used. I think in case of `rerun` and of `runall` this is not appropriate....
I consider pythontex quite mature already (version 0.18) and also quite important and almost in one line with bibtex, makeindex and makeglossaries. Also the way pythontex is used is comparable:...
Currently, I just include code if it is more than a snipped with `pycode` or `octavecode` but this is quite messy. First of all my code checker constantly complains and...
pythontex works as bibtex, makeindex, makeglossaries: invoke latex, then the tool then latex again. All these tools give indication that sth is wrong with output pdf indicating that rerun is...