-
-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flask-AppBuilder broken after new update - cannot import name 'SelectFieldBase' from 'wtforms.fields' #861
Labels
bug
Unexpected behavior
Comments
raimundovidaljunior
changed the title
Flask-AppBuilder broken after new update
Flask-AppBuilder broken after new update - cannot import name 'SelectFieldBase' from 'wtforms.fields'
Oct 21, 2024
Thank you for your report. Can you confirm that #862 solves your import issues? |
Just to confirm. Our CI in Airflow started to detect it as well https://github.com/apache/airflow/actions/runs/11435317651/job/31810505554#step:16:24 I am going to test the fix now. |
The fix is in the 3.2.1 release. |
Thank you. Confirmed it solved our CI issue. |
Thanks for super fast reaction @azmeuk ! |
potiuk
added a commit
to potiuk/airflow
that referenced
this issue
Oct 21, 2024
WTForms are limited to 3.2.0 because of the error in tests. We technically do not need it directly as this is a dependency of Flask-WTF, but we need to specify it here to add the limitation The issue to track it is https://github.com/pallets-eco/wtforms/issues/863 Note. 3.2.0 has been broken because of imports pallets-eco/wtforms#861 which was fixed in 3.2.1, but after import was fixed, the tests started to work with 3.2.1 when the issue 863 is fixed, we should likely leave the line below and specify !=3.2.0,!=3.2.1
potiuk
added a commit
to apache/airflow
that referenced
this issue
Oct 21, 2024
WTForms are limited to 3.2.0 because of the error in tests. We technically do not need it directly as this is a dependency of Flask-WTF, but we need to specify it here to add the limitation The issue to track it is https://github.com/pallets-eco/wtforms/issues/863 Note. 3.2.0 has been broken because of imports pallets-eco/wtforms#861 which was fixed in 3.2.1, but after import was fixed, the tests started to work with 3.2.1 when the issue 863 is fixed, we should likely leave the line below and specify !=3.2.0,!=3.2.1
jscheffl
pushed a commit
to jscheffl/airflow
that referenced
this issue
Oct 21, 2024
WTForms are limited to 3.2.0 because of the error in tests. We technically do not need it directly as this is a dependency of Flask-WTF, but we need to specify it here to add the limitation The issue to track it is https://github.com/pallets-eco/wtforms/issues/863 Note. 3.2.0 has been broken because of imports pallets-eco/wtforms#861 which was fixed in 3.2.1, but after import was fixed, the tests started to work with 3.2.1 when the issue 863 is fixed, we should likely leave the line below and specify !=3.2.0,!=3.2.1 (cherry picked from commit 979d750)
jscheffl
added a commit
to apache/airflow
that referenced
this issue
Oct 21, 2024
WTForms are limited to 3.2.0 because of the error in tests. We technically do not need it directly as this is a dependency of Flask-WTF, but we need to specify it here to add the limitation The issue to track it is https://github.com/pallets-eco/wtforms/issues/863 Note. 3.2.0 has been broken because of imports pallets-eco/wtforms#861 which was fixed in 3.2.1, but after import was fixed, the tests started to work with 3.2.1 when the issue 863 is fixed, we should likely leave the line below and specify !=3.2.0,!=3.2.1 (cherry picked from commit 979d750) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
utkarsharma2
pushed a commit
to apache/airflow
that referenced
this issue
Oct 23, 2024
WTForms are limited to 3.2.0 because of the error in tests. We technically do not need it directly as this is a dependency of Flask-WTF, but we need to specify it here to add the limitation The issue to track it is https://github.com/pallets-eco/wtforms/issues/863 Note. 3.2.0 has been broken because of imports pallets-eco/wtforms#861 which was fixed in 3.2.1, but after import was fixed, the tests started to work with 3.2.1 when the issue 863 is fixed, we should likely leave the line below and specify !=3.2.0,!=3.2.1 (cherry picked from commit 979d750) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
harjeevanmaan
pushed a commit
to harjeevanmaan/airflow
that referenced
this issue
Oct 23, 2024
WTForms are limited to 3.2.0 because of the error in tests. We technically do not need it directly as this is a dependency of Flask-WTF, but we need to specify it here to add the limitation The issue to track it is https://github.com/pallets-eco/wtforms/issues/863 Note. 3.2.0 has been broken because of imports pallets-eco/wtforms#861 which was fixed in 3.2.1, but after import was fixed, the tests started to work with 3.2.1 when the issue 863 is fixed, we should likely leave the line below and specify !=3.2.0,!=3.2.1
PaulKobow7536
pushed a commit
to PaulKobow7536/airflow
that referenced
this issue
Oct 24, 2024
WTForms are limited to 3.2.0 because of the error in tests. We technically do not need it directly as this is a dependency of Flask-WTF, but we need to specify it here to add the limitation The issue to track it is https://github.com/pallets-eco/wtforms/issues/863 Note. 3.2.0 has been broken because of imports pallets-eco/wtforms#861 which was fixed in 3.2.1, but after import was fixed, the tests started to work with 3.2.1 when the issue 863 is fixed, we should likely leave the line below and specify !=3.2.0,!=3.2.1
utkarsharma2
pushed a commit
to apache/airflow
that referenced
this issue
Oct 24, 2024
WTForms are limited to 3.2.0 because of the error in tests. We technically do not need it directly as this is a dependency of Flask-WTF, but we need to specify it here to add the limitation The issue to track it is https://github.com/pallets-eco/wtforms/issues/863 Note. 3.2.0 has been broken because of imports pallets-eco/wtforms#861 which was fixed in 3.2.1, but after import was fixed, the tests started to work with 3.2.1 when the issue 863 is fixed, we should likely leave the line below and specify !=3.2.0,!=3.2.1 (cherry picked from commit 979d750) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
ellisms
pushed a commit
to ellisms/airflow
that referenced
this issue
Nov 13, 2024
WTForms are limited to 3.2.0 because of the error in tests. We technically do not need it directly as this is a dependency of Flask-WTF, but we need to specify it here to add the limitation The issue to track it is https://github.com/pallets-eco/wtforms/issues/863 Note. 3.2.0 has been broken because of imports pallets-eco/wtforms#861 which was fixed in 3.2.1, but after import was fixed, the tests started to work with 3.2.1 when the issue 863 is fixed, we should likely leave the line below and specify !=3.2.0,!=3.2.1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actual Behavior
Flask-AppBuilder is broken After removal of SelectFieldBase from the src/wtforms/fields/init.py
this is in consequence breaking a few airflow packages like so
this started happening today so I assume it was due to the new release, more specifically this
Expected Behavior
expected behaviour is having Flask-AppBuilder work properly
Environment
The text was updated successfully, but these errors were encountered: