Helm chart failing to install extra Python package requirements with Superset 5.0.0rc1

[JZ6]

Bug description

I pip installed authlib in the bootstrap script, then helm deployed to a gke cluster.
But still getting ModuleNotFoundError: No module named 'authlib'.

Screenshots/recordings

Superset version

5.0.0 rc1

Python version

3.11

Node version

18

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot]

Hey @JZ6! I'm here to help you out with any bugs, questions, or contributions. Let's tackle this issue together!

A similar closed issue suggests that since Authlib is an optional dependency, it might be necessary to add an extras_require to setup.py and include a note in the documentation indicating that Authlib is required when setting up OAuth ^[1].

Additionally, it's important to note that Python 3.9 support is deprecated in Superset 5.0, which could potentially affect module imports. It is recommended to use Python 3.11, with Python 3.10 still supported ^[2]. You might want to consider upgrading your Python version to see if it resolves the issue.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[JustGui]

I had a similar issue trying to add libraries too in my Dockerfile, the issue was that Superset now runs using the virtual environment in /app
So I fixed the issue by running /app/.venv/bin/pip install instead of pip install
You might need to install pip before too: /app/.venv/bin/python -m ensurepip

[JZ6]

I had a similar issue trying to add libraries too in my Dockerfile, the issue was that Superset now runs using the virtual environment in /app So I fixed the issue by running /app/.venv/bin/pip install instead of pip install You might need to install pip before too: /app/.venv/bin/python -m ensurepip

thanks for the solution, i think this should be fixed before 5.0 release as this would break for everyone who uses helm charts to install some packages right

[mistercrunch]

Oh right, we use uv now, it really helps with build times, seem we may need to update some docs if they're not already (?)

[mistercrunch]

Here: #32239

[JZ6]

Here: #32239

thanks for the fix!