Matthew Seal

> sigh Do we need to sigh? > This statement should have been made years ago and featured prominently in the docs Fair that it's not documented. I've said this...

If folks have proposals to help mitigate the risks of adding tooling complexity or making the outputs clear about what executed in the different interfaces for viewing notebooks that is...

In discussing the topic in today's weekly nteract meeting, I proposed that we could mark cells to be commented instead of strictly skipped by tag. This would preserve the execution...

Noted. Probably possible to implement both if it's done.

Ok we're going to start with `--remove-tagged-cells={tag}`, not as a regex but a fixed string match to keep it as simple as possible. I'm opting for `remove` over `skip` to...

> Any update on this? I see a message from June 2020 about implementing `--remove-tagged-cells={tag}` option. Is this still planned and being worked on? Yes, I just had a child...

So papermill doesn't do scheduling by itself. Instead think of it as a tool for executing notebooks that's easy to pass information into. In the provided examples alpha and ratio...

https://stackoverflow.com/questions/132971/what-is-the-windows-version-of-cron links a few options depending on your OS version.

I can attest that the bash on windows approach works quite well for 99% of tasks (though I haven't tried airflow explicitly with this) :D

So in papermill we already expose execution time stamps for each cell: ``` "metadata": { "papermill": { "duration": 0.056221, "end_time": "2019-10-25T16:34:18.177909", "exception": false, "start_time": "2019-10-25T16:34:18.121688", "status": "completed" }, ``` To...