[marcoalopez]

Jupiter is excellent at what it is designed for. For example, my usual workflow is as follows: when I develop a tool or model, I do so in a plain Python file. I then import the file from the notebook to create figures, demonstrations, documentation and so on, resulting in an immediate document that my colleagues and I can easily use for discussion. It's as simple and effective as that. It is also a great tool for teaching coding to beginners. Of course, notebooks are not designed for code development. Also, nowadays, if you want to, you can open notebooks in dedicated apps.

[drnick1]

Any reason your colleagues can't run the original Python script? It seems like your workflow entails going back and forth between script and notebook or having to make changes in two places to keep both versions in sync.

Then there is also the issue that notebooks are too complex to version-control effectively.

[marcoalopez]

Not all of my colleagues know how to code, but they do know how to interpret results, plots and so on (I'm in science, by the way). In my case, I am not interested in version controlling the notebook; it's just for quick prototyping and discussing ideas. I only need to version control the Python file. Also, colleagues who don't code (or dislike coding) can easily modify parameters in the notebook and obtain different results immediately with no additional effort.

[bragr]

>make changes in two places to keep both versions in sync.

That's not how Python imports work. You can import in the notebook just like any other Python script.