-
Notifications
You must be signed in to change notification settings - Fork 67
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
Compile generates ImportError
#30
Comments
These sorts of issues are usually related to the version of various python pip packages and the version of pygments itself. |
so, how should I install PythonTeX 0.18dev? after upgrading from 0.17 to 0.18v, will |
I don't think the issue is with pythontex. So long as it is v0.17 or later, you should be okay. I think the issue might be with the version of pygments. Can you confirm that version? You can run |
Pygments version 2.7.4, (c) 2006-2021 by Georg Brandl.
On February 3, 2021 at 15:36 GMT, Mykel Kochenderfer <[email protected]> wrote:
I don't think the issue is with pythontex. So long as it is v0.17 or later, you should be okay. I think the issue might be with the version of pygments. Can you confirm that version? You can run pygmentize -V.
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#30 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABIHE7NPQV7HJRWP3GFN323S5FUOJANCNFSM4XAAORHQ).
|
I think this is the latest version for the `Pygments`.
On February 3, 2021 at 17:37 GMT, Tianchi Chen <[email protected]> wrote:
Pygments version 2.7.4, (c) 2006-2021 by Georg Brandl.
On February 3, 2021 at 15:36 GMT, Mykel Kochenderfer <[email protected]> wrote:
I don't think the issue is with pythontex. So long as it is v0.17 or later, you should be okay. I think the issue might be with the version of pygments. Can you confirm that version? You can run pygmentize -V.
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#30 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABIHE7NPQV7HJRWP3GFN323S5FUOJANCNFSM4XAAORHQ).
|
I think the repo is pointing to an old version of the lexer. Would you mind trying updating the lexer by running:
|
|
Hmm... I get something different:
|
I remember that when I first install it, I got the same thing as you posted. everything installed successfully. I got that because it is already installed. |
I uninstalled pygments and reinstall it.
But the |
Also, my test run are successfull.
I am also attaching all the message shown in my terminal
|
The issue is not with pygments. That is installed correctly. The issue is that your python installation isn't using the current version of pygments-julia: https://github.com/sisl/pygments-julia The reason I know this is that the error message is complaining about the use of |
Ok, Thank you. I followed that link and install it again. The error seems gone right now.
What is this related to? is it about also when I tried
it does not seems to work for excluding chapters. I have spacevim installed. |
@mossr ? |
You can try to revert Weave.jl back to 0.10.2 (see this thread: JunoLab/Weave.jl#391 (comment)) |
ok, now it works. Thanks!
did I do something wrong for this partial compile? |
Remove the spaces around the make compile CHAPTER='introduction chapter2\/introduction' I'll update the README to reflect this. |
ok, it works now. Thanks for the clarification.
…On Wed, Feb 3rd, 2021 at 9:13 PM, Robert Moss ***@***.***> wrote:
You can try to revert Weave.jl back to 0.10.2 (see this thread: JunoLab/Weave.jl#391
(comment) (
JunoLab/Weave.jl#391 (comment) ) )
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (
#30 (comment)
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/ABIHE7PMNGPWN2B5QE5K2ODS5H7FTANCNFSM4XAAORHQ
).
|
Following the instruction, I have the following compiling error after
make compile
. I am not sure which issue is this. Is it related to some python packages? But this error does not seems to affect the output of the pdf. IThe text was updated successfully, but these errors were encountered: