Re: [jupyter] Re: jupyter nbconvert - recursive option request?

To that point - on these kind of "quite useful but out-of-scope for a tightly-scoped project" hacks, I think documentation (or places like the community forum ) are a good place for these kinds of tips On Mon, Aug 19, 2019 at 2:45 PM Matthew Seal wrote: > As one

Re: [jupyter] Re: jupyter nbconvert - recursive option request?

As one of the nbconvert maintainers, I'd say we're unlikely to add such a feature to nbconvert. As Roland mentioned it's easy to script or manage above the library and it would make the code harder to maintain over the long term. And +1 for Issues / PRs being the best way to interface for feature

[jupyter] Re: Custom kernel launch control

Hi Amar - great questions. Yes, you should be able to accomplish both of these requests using Enterprise Gateway. 1. You could create different kernel specifications, one that is CPU-based, another that is GPU-based. Since each will have its own copy of kernel-pod.yaml file, you can modify

[jupyter] Re: jupyter nbconvert - recursive option request?

Personally, I don't think that nbconvert should bother with searching input files in a directory structure. As your post shows, this is easily added through scripting, without causing extra effort for the nbconvert maintainers. Nevertheless, you can always open a feature request: