This message was deleted.

This seems like an issue with the conda env environment in general. I haven't use ipython extensions heavily but my guess is that your ipython copy in the

analysis

env is finding your

profile_default

and then trying to load the extensions. I can think of a couple options: 1. disable the extensions globally 2. disable them locally (not sure how to do this but perhaps you can create a

jupyter/.ipython/profile_default

that is local to the analysis conda env 3. install the sql extensions (and any others) in the conda env thoughts?

Looking at ploomber’s interact.py, I see it calls start_ipython and links to this ipython issue One option could be to set profile to none in start_ipython config - though I couldn’t find any example of that. I can’t disable/change default profile as that is used for the notebook interface. I understand this is probably a low priority issue to solve, though here are my thoughts: Is loading default config a good thing? I would say no. As default config is meant for default environment - whereas in production almost always ploomber will not be running in default environment. In such a scenario I can see 3 options: • Ploomber starts ipython in a way so that no profile gets loaded (either settting argv or config in start_ipython) • Ploomber ships with its own profile and uses that. • There is some command line or config param which lets a user specify profile to use with ploomber.

Ah interesting. Thanks for sending this, I'll dig into this a bit more. Does this mean Ploomber works well except for “Ploomber Interact”? Or is the whole installation broken?

I tried ploomber build with one task with ipynb source. It actually ran and completed the build successfully even though it did throw errors about missing ipython modules.

thanks for the update! was it the same error as before (fail to load sql module)? - I'll open an issue on github so we keep track of this. i agree with your earlier arguments about isolating ploomber from the system wide config

Yes. It printed warnings on two modules. One being sql and other being a private package beatrix-jupyterlab on gcp vertex ai workbench instances:

❯ pip show beatrix-jupyterlab
Name: beatrix-jupyterlab
Version: 3.1.7
Summary: Beatrix Notebooks extension package
Home-page: <http://go/notebooks-frontend>
Author: Vertex AI Notebooks FE Team
Author-email: <mailto:cloud-ai-frontend-notebooks@google.com|cloud-ai-frontend-notebooks@google.com>
License: Apache License 2.0
Location: /opt/conda/lib/python3.7/site-packages
Requires: google-auth, google-cloud-bigquery, google-cloud-bigquery-storage, google-cloud-storage, jinja2, jupyter-server, jupyterlab, matplotlib, pandas, pexpect, psutil, pyarrow, pyjwt, requests, tqdm
Required-by:

great, thanks for the feedback! I'll look into this to see how we can fix it. feel free to send any other questions!