quarto publish problem: can not start python3 kernel

[xinhuaChenW]

Could you please help?

When Quarto was publishing new '.qmd' containing python codes, it stucked at 'Starting python3 kernel'. It appears that Quarto can't start python kernel.
figure 1.

However, when the python code cell is removed, the .qmd file can be published successfully. So, the problem should be correlated to the python kernel.

The path to the python kernel is right, however, Quarto just can't start the kernel. I have no idea what is going on.

figure 2. the python interpreter pathway in setting.json file.

figure 3. the pathway of the current running python interpreter in VSCode is exactly the same with the pathway in setting.json as in figure 1.

And it makes me more confused that the python code in this '.qmd' file can be run if I click the 'Run Cell ' button and it gives correct outputs.

figure 4 and 5. python code can give output correctly if the code cell is executed alone.

setting.json about python interpreter path is as following.

    "python.defaultInterpreterPath": "D:\\Anaconda\\python.exe",
    "editor.inlineSuggest.enabled": true,
    "python.condaPath": "D:\\Anaconda\\_conda.exe",

[eitsupi]

I don't think the quarto executed on the command line and vscode settings are relevant.

[bvancil]

I figured out the problem, for me at least. I was inadvertently allowing prerelease versions of jupyter-client and notebook python packages. Once I pinned those to stable release versions, quarto check jupyter worked fine. This might be a heads-up to the Quarto devs that jupyter-client 8.0.0a breaks things.

[lindsay-fredrick]

For what it's worth, the current version still breaks things - I've pinned jupyter_client to 7.3.5 for now. jupyter-client 8.0.1 is no longer pre-release so I just found out today that it isn't playing nicely when I tried to render my github-page without a pinned version.

[cscheid]

@lindsay-forestell If you can produce a minimal case where this happens for you consistently, we'd appreciate a bug report, thank you.

[xinhuaChenW]

I haven't tried this recently? @cxh76153264 , have you? Maybe we should submit this as an issue rather than a discussion.

Sorry to reply so late. bvancil. Glad to recieve a good news from you. Since I encountered that problem last time, I haven't used quoto for a long time. I've been busy with other more urgent things these days and haven't finished yet. I admire you for continuously trying to research this issue and finding a solution. I'm also interested because maybe I can use quarto in VScode happily again (cause no need to swicth to another IDE). When I have some free time, I'll try your method. Thank you for your reply, I really appreciate it!!

[xinhuaChenW]

@bvancil It is working well with jupyter-client 7.4.8, facinate!! Thank you !!

[benabel]

I also add to pin jupyter_client==7.4.7 to build with quarto on a docker-image using ubuntu:rolling. If not quarto hanged on ...Starting jupyter kernel

[cscheid]

If you use one of our latest prereleases (as of yesterday) then you should be able to make things work with jupyter_client 8+. Our very latest prerelease (being built just now) should work with both versions.

[xinhuaChenW]

Thank you for your reply! Will give it a try later. Happy about using quarto again.

[Mouli04]

I too facing the same error. Any fix...?

[dragonstyle]

We just published Quarto 1.2.335 which should fix this issue.

https://quarto.org/docs/get-started/

[benabel]

I confirm this is fixed on my system with v1.3.159. Thank you.