I'd like to give more people a chance to weigh in on a design decision regarding nbconvert.
Since the --execute option was added to nbconvert back in 2014 (when it was still part of IPython), it has had a configurable per-cell execution timeout. By default, code that takes longer than 30 seconds is cut off, and nbconvert fails. A different limit can be set, or the timeout can be disabled entirely, so that it will leave the code running for as long as it takes. There is a proposal to disable the timeout by default, so people who wanted any timeout would have to set it explicitly. I think this would make sense if we were designing a new feature today, but I'm still trying to work out whether it's worth changing a default that people have had several years to get used to. If we do change it, I'd like to give warning messages first, but providing warnings doesn't necessarily mean people will see them. Here's the issue for more in-depth discussion: https://github.com/jupyter/nbconvert/issues/791 Thanks, Thomas -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+unsubscr...@googlegroups.com. To post to this group, send email to jupyter@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/ea23bf4a-c380-4b55-b7a0-65f0611d4928%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
