Eduardo Blancas
Eduardo Blancas
Hi, I realized that using tildes and double newline for markdown breaks conversion to ipynb. I'm using jupytext 1.13.0. Example (double newline between `import` and `def`): ```md ~~~python import math...
Currently, we throw an error if the notebooks are missing a parameters cell, but this is too restrictive; we should show a warning instead. I think this does don't happen...
in the docs we have an example that looks like this: ```yaml tasks: - source: random-forest.py name: random-forest- product: 'n_estimators=[[n_estimators]]/criterion=[[criterion]].html' grid: n_estimators: [5, 10, 20] criterion: [gini, entropy] ``` [link](https://docs.ploomber.io/en/latest/api/spec.html#tasks-grid)...
To inject cells manually, users can run: ``` ploomber nb --inject ``` However, if the same source appears more than once. Ploomber will arbitrarily select one of the tasks and...
Our README has too many options and people get lost. It should be clear how to get started. I think it should only give two options: running the onboarding tutorial...
When tasks have long titles, the text goes over the limits of the task. We should adjust the text size automatically to fit the node: 
[Our Jupyter integration](https://docs.ploomber.io/en/latest/get-started/basic-concepts.html#the-cell-injection-process) requires loading the user's pipeline whenever they open a notebook ([source code](https://github.com/ploomber/ploomber/blob/master/src/ploomber/jupyter/manager.py#L104)). However, the loading process will fail if the `pipeline.yaml` has issues. For example, if the...
when we make a new release, we tag the commit. however, the unit tests are not triggered when this happens: https://github.com/ploomber/ploomber/tree/0.20
the integration tests fail very often due to time out. it's often different tests: https://github.com/ploomber/ploomber/actions/runs/2797564899/attempts/1
when users have a breakpoint in a notebook task: ```python from pdb import set_trace set_trace() ``` The `next` command won't work as expected since notebooks are executed differently: they are...