squalou opened a new issue, #31162: URL: https://github.com/apache/superset/issues/31162
### Bug description I'm not sure if this is a bug, or intended behavior. ### What I do - from superset master (more precisely tag 4.1.1rc1 at the moment) - docker build - docker run using previous version (3. something) superset_config.py ... using a mysql database for storage - I do have some postgresql connections configured to some other dbs ### Result Superset will not start, I get the error ``` ModuleNotFoundError: No module named 'MySQLdb' ``` ### Workaround I did edit `Dockerfile` added some packages to image (`pkg-config python3-dev default-libmysqlclient-dev build-essential`) I added `mysqclient` to `requirements/base.txt` Then rebuild image => superset starts. In order to have my posgresql connections work, I added `psycopg2` to `requirements/base.txt` too. And finally things work. ### Question Is it expected (and if so, no problem, I'll keep doing it at each upgrade, not an issue), or am I missing something ? Thanks for reading ! ### Screenshots/recordings _No response_ ### Superset version master / latest-dev ### Python version 3.10 ### Node version 18 or greater ### Browser Firefox ### Additional context _No response_ ### Checklist - [X] I have searched Superset docs and Slack and didn't find a solution to my problem. - [X] I have searched the GitHub issue tracker and didn't find a similar bug report. - [X] 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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
