Bug description
After installing superset with Python Virtual Environment as described in official guide, superset cannot be launched due to the following errors:
- superset failed to create app. TypeError: Field.init() got an unexpected keyword argument 'minLength'
- no module named "flask_limiter.wrapper"
but changing marshmallow version as suggested in https://github.com/apache/superset/issues/23577 and changing flask_limiter version in 3.5.1
the problems are solved
Screenshots/recordings
No response
Superset version
5.0.0
Python version
3.11
Node version
I don't know
Browser
Not applicable
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.
- [ ] 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.
Comment From: dosubot[bot]
Hi @PCore-D! I'm Dosu and I’m helping the superset team.
Superset 5.0.0 is not compatible with marshmallow 4.x—this causes the Field.__init__() got an unexpected keyword argument 'minLength' error. The fix is to use marshmallow 3.26.1, which is the version pinned in Superset's requirements and confirmed by maintainers as the correct workaround until a future patch release includes a permanent fix [source].
For the no module named "flask_limiter.wrapper" error, this happens because newer flask-limiter versions removed or changed the wrapper module. Superset 5.0.0 pins flask-limiter to 3.12 for compatibility, so using 3.12 (or 3.5.1, which also works for some users) resolves this issue [source].
If you install Superset via pip or in certain environments, dependency resolution might still pull in incompatible versions. The safest approach is to manually install the pinned versions:
pip install marshmallow==3.26.1 flask-limiter==3.12
This aligns your environment with the versions tested and supported by Superset 5.0.0 [source].
Let me know if you need more details or run into other dependency issues!
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: rusackas
It's bumped on master and should be using these versions in 6.0. Not sure if we should backport these versions to 5.0 in the next patch or not. Thoughts, @sadpandajoe ?