-
Notifications
You must be signed in to change notification settings - Fork 567
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
nbconvert 6.0.0 causing build failures due to TemplateNotFound error #1369
Comments
* For service deletion, spin the del event storm commmand off in a schedcoro so it is out of line with the bottom half of the nexus function. This changes the del event semantics by executing a del handler without the presence of the supporting package, but breaks a nested nexus loop action. * Ensure that cull is passed in the coreQueueGets call, since it was missed * Temporarily pin nbconvert until jupyter/nbconvert#1369 is resolved.
Hey @vEpiphyte thanks for reporting! The way custom templates are done is one of the main changes in nbconvert 6.0, and the main reason for the major version bump indicating backward incompatibility. You can check out the documentation here: https://nbconvert.readthedocs.io/en/latest/customizing.html There is also a tutorial in the works on how to create more sophisticated templates. |
I'm seeing the same problem on a Mac. |
@anpaz-msft thanks for reporting. Your issue is unrelated to the original one (which was expected behavior). Yours appear to be a legitimate bug with |
@anpaz-msft actually, I am not reproducing your issue. Could you please report the output to
and the content of your |
@SylvainCorlay Thanks for following up. I look forward to seeing the tutorial about migrating old templates. |
I had the same problem on Windows 10, and after reading @SylvainCorlay reply, I unistall nbconvert and then reinstalled it without the flag I think @SylvainCorlay is correct, something goes wrong when using the My directory |
Tutorials, docs updates, and some fixes for a few issues related to this have all been resolved. I'm going to close this issue as I believe it's addressed |
I faced the same issue using nbconvert version ValueError: No template sub-directory with name 'report' found in the following paths: I used the command suggested in docs: jupyter-nbconvert --to pdf --no-input --no-prompt --template report nb.ipynb However, rolling back to version |
The same on Windows 10 (without admin rights). 5.6.1 fixed the issue, while 6+ versions are still bagged. |
When executing nbconvert to convert a jupyter notebook into RST format with a custom template that extends
rst.tpl
, I receive an exception forjinja2.exceptions.TemplateNotFound: display_priority.j2
. We are using a custom template to extend therst.tpl
file in order to surpress output blocks in the RST output which have been marked with thehide_code
jupyter extension. Since we run notebooks as part of our unittests to ensure our documentation is up-to-date, this is causing build failures for our project (vertexproject/synapse). This can be seen in vertexproject/synapse#1876 and https://app.circleci.com/pipelines/github/vertexproject/synapse/4660/workflows/dcb1e54f-fc51-49fd-9134-e88ef80c5c7d/jobs/19312This is the custom template file
We're not currently constraining the version of the nbconvert library installed, instead relying on the packages installed by installing the
jupyter
library.I do not have a minimal test case example, but it is reproducible.
This eventually fails with the following error
Executing the conversion without the
--template
argument provided does work to convert the notebook, but includes the information I want to drop.I did try modifying the
index.rst.j2
file to load'base/display_priotiy.j2
and that did successfully execute my builds, but I don't know if that change has other ramifications for nbconvert at a larger scale or not.This is using nbconvert 6.0.1. I have also confirmed that 6.0.0 also fails. 5.6.1 worked fine.
The following is a dump of libraries from
python -m pip freeze
the venv used aboveThe text was updated successfully, but these errors were encountered: