Closed johnnychen94 closed 4 years ago
Yep, I know how to fix it. I'll post tomorrow.
The simplest fix is to change the version in pythontex.sty
in this repository:
# ./pythontex.sty
- \newcommand{\pytx@packageversion}{0.17dev}
+ \newcommand{\pytx@packageversion}{0.17}
But after running a diff between pythontex.sty
in this repository and original pythontex v0.17, the relavent differences are:
- \ifstrequal{#1}{julia}{\makepythontexfamily[pyglexer=julia1]{julia}}{}%
- \ifstrequal{#1}{juliacon}{\pgfkeys{/PYTX/family, name=juliacon, default, pyglexer=jlcon1}%
- \expandafter\xdef\csname pytx@macroformatter@juliacon\endcsname{\pytx@tmp@pprinter}%
- \expandafter\gdef\csname pytx@fvsettings@juliacon\endcsname{}%
- \expandafter\xdef\csname pytx@pyglexer@juliacon\endcsname{\pytx@tmp@pyglexer}%
- \expandafter\xdef\csname pytx@pygopt@juliacon\endcsname{\pytx@tmp@pygopt}%
- \expandafter\xdef\csname pytx@console@juliacon\endcsname{\pytx@tmp@console}%
- \AtEndDocument{\immediate\write\pytx@codefile{pygfamily=juliacon|%
- \csname pytx@pyglexer@juliacon\endcsname|%
- \csname pytx@pygopt@juliacon\endcsname}%
- }%
- \pytx@MakeCodeFV{juliacon}%
- \newenvironment{juliaconsole}%
- {\VerbatimEnvironment
- \def\pytx@type{juliacon}%
- \pytx@ConfigPygments
- \begin{juliaconcode}}%
- {\end{juliaconcode}%
- \ifbool{pytx@opt@autoprint}{}{\printpythontex{}}}}{}%
- \ifstrequal{#1}{jl}{\makepythontexfamily[pyglexer=julia1]{jl}}{}%
+ \ifstrequal{#1}{julia}{\makepythontexfamily[pyglexer=julia]{julia}}{}%
+ \ifstrequal{#1}{juliacon}{\makepythontexfamily@con[jlcon]{julia}}{}%
+ \ifstrequal{#1}{jl}{\makepythontexfamily[pyglexer=julia]{jl}}{}%
If these are acceptable, then we could delete pythontex.sty
from this repository safely.
Edit: oh julia1
is your custom-built pygments hmmm... as a template probably adding this would make the project too complicated?
Looks like pythontex v0.17 (it was v0.17-dev) breaks the pipeline, I'll need some time to investigate it, just open an issue here in case others meet the same problem.