Bug description
Description:
I encountered an error when testing a database connection in Superset. The request fails with:
ModuleNotFoundError: No module named 'pip'
Stack trace (relevant part):
File "/app/.venv/lib/python3.11/site-packages/shillelagh/functions.py", line 12, in <module>
import pip
ModuleNotFoundError: No module named 'pip'
This originates from the Shillelagh dependency, which attempts to import pip at runtime.
Steps to reproduce:
- Deploy Superset in a minimal Python environment (e.g., Docker with Python 3.11 slim image)
- Create a virtual environment without pip (or where pip is not available)
- Attempt to test a database connection via the UI
- Observe failure
Expected behavior:
Testing a database connection should not depend on the presence of pip as an importable module.
Actual behavior:
The request fails due to ModuleNotFoundError: No module named 'pip'.
Environment:
- Superset version: 6.0.0
- Python version: 3.11
- Deployment: Docker (minimal image)
- OS: (e.g. Debian slim)
Screenshots/recordings
Superset version
master / latest-dev
Python version
3.11
Node version
18 or greater
Browser
Chrome
Additional context
No response
Checklist
Bug description
Description:
I encountered an error when testing a database connection in Superset. The request fails with:
Stack trace (relevant part):
This originates from the Shillelagh dependency, which attempts to import
pipat runtime.Steps to reproduce:
Expected behavior:
Testing a database connection should not depend on the presence of
pipas an importable module.Actual behavior:
The request fails due to
ModuleNotFoundError: No module named 'pip'.Environment:
Screenshots/recordings
Superset version
master / latest-dev
Python version
3.11
Node version
18 or greater
Browser
Chrome
Additional context
No response
Checklist