Closed NickCH-K closed 1 year ago
Thank you so much for reporting this! This appears to have been a regression in Quarto v1.3 so perhaps you were running v1.3 on Mac on v1.2 on Windows? In any case I reproduced using your test code and verified that the following fixes it and results in the plots showing up as expected: https://github.com/quarto-dev/quarto-cli/commit/27162c0cc93ea639d96f83b6f6f52223069eac71
The fix is on our pre-release v1.4 and we have also back ported the fix to v1.3 stable (available now as v1.3.357) and have
Fantastic, thank you!
This is an issue that I originally thought was with Seaborn but after posting the issue there it appears to be with Quarto.
Here's the issue:
fig = plt.figure()
, thenso.Plot().on(fig)
. The second one is printed usingseaborn.objects
directly (without.on(fig)
). These graphs render properly in Jupyter.Note:
objects
seaborn graphs.sns.lineplot()
works fine.inline
ornotebook
) doesn't seem to matter.Here is the code for a Jupyter notebook that exhibits the issue. Note that I am using
p.plot()
here, but the same issue occurs if you don't save the plot asp
and instead just haveso.Plot()
on a line by itself.(code chunk 1, this renders properly on both Windows and Mac)
(code chunk 2, this does not show up in the resulting document on Mac, but it works fine on Windows)