Matthew Seal

No need to get hostile. I happen to maintain both code bases, and at the time chdir was written in papermill the nbconvert (where nbclient came from), jupyter_client, and ipykernel...

Yes, though I re-looked at the code involved and I believe the cwd used to impact the `developing-new-i-o-handlers` but hasn't since a refactor a while back. This actually only leaves...

The output notebook is not the cause here. It's the kernel's ZMQ buffer overflowing when communicating back the outputs of execution. Instead you may want to set the log level...

Yes. You can use `--log-output` and it will stream the logs to the command line live. To note, older versions of nbconvert won't live log, so make sure you have...

So when setting `log_output` in a python script it's making python log the output to the `logging.getLogger('papermill')`. This lets you control how the log message propegates e.g.: ``` logging.basicConfig(level='INFO', format="%(message)s")...

Today it's kind of a pain afaik. You could try adding `%config c.InteractiveShell.pdb = False` at the top of your notebook. If that works you could also make a [custom...

The `log_output` is a little more specific of a flag: >@click.option( > '--log-output/--no-log-output', > default=False, > help="Flag for writing notebook output to the configured logger.", >) It's to control the...

You can control this by setting the logging basic config: `logging.basicConfig(level=log_level, format="%(message)s")`, or by setting papermill or nbconvert's logger specifically at runtime. The reason we only set the basic config...

For python3 we're now using black to format for python dependencies via #455 in the next release. For other languages we don't have a standard solution as of yet. A...

@tgandor You can set the `--log-level ERROR` to suppress warnings. You may want to consider however that you're erasing your execution logs by not logging or saving the notebook result....