Thomas Kluyver

We probably need to find a more efficient way to do that - it makes an HTTP request to each server to get the list of running notebook sessions.

From a user perspective, I like having the sessions readily available there - especially as I think many users will run with all their sessions in just one or two...

The [spec for JSON](https://tools.ietf.org/html/rfc8259) essentially says it's stored in UTF-8 unless a specific 'closed ecosystem' needs something different: > JSON text exchanged between systems that are not part of a...

I broadly agree with Min, but I think it's worth exploring some way to connect notebooks to environments other than exposing environments as kernelspecs: - If I reopen a notebook...

metadata _is_ an expansion area - it would be fine for an extension to use something like `metadata.conda_env` to specify something like that. I'm not sure that we gain anything...

Maybe it would be useful to have some kind of tool that could create an environment from a specification file and mark a set of notebooks (e.g. notebooks in the...

Have a look at nbparameterise: https://github.com/takluyver/nbparameterise In particular, this example sounds quite similar to what you're asking: https://github.com/takluyver/nbparameterise/blob/master/examples/batch.py

Specifically, they don't currently mention language_info

(there may well be other problems too, but that's one omission I've noticed)

I see code in the notebook UI that checks `deletable`. There's nothing to implement for it in nbformat.