This message was deleted.

What's the use case? Usually when you consume a python file, and execute it, it's usually the same. We have an open issue on multiple formats for user products https://github.com/ploomber/ploomber/issues/673

the idea of having a notebook output is that the ipynb file can contain charts and tables in a standalone file. if it's a script, that isn't possible. what's the use case?

We wnted ti use an .ipynb file as source, generate a .py file as product, and finally import the product in another task

Is there a reason not to consume the product .ipynb as an input? Also what you could do is running the source as a .py and then consume it (since it’s a .py there’s no context like in notebooks so you can have a generic input).

1- Dimension of the file

Ah ok. Sounds like pairing will work for you. Pairing allows you to have two sources (py and ipynb) and keep them synced https://docs.ploomber.io/en/latest/user-guide/editors.html

Wonderful, thanks!