-
Notifications
You must be signed in to change notification settings - Fork 310
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
"ValueError: too many values to unpack" with SQLAlchemy 1.2.2 #324
Comments
That's part of WTForms, not Flask-WTF. |
@lepture what do you want to do here? WTForms isn't being updated, but I don't really want to pull this into Flask-WTF. |
@davidism Oh, silly me! I should have seen that it was an issue directly in WTForms. What do you mean when you said WTForms isn’t being updated? Is the project no longer maintained? Thanks! |
It's still stable and usable, but I don't have access to make new releases, only to merge stuff. |
Hmm. Should I open a similar issue or PR over in WTForms for someone to review and merge, then a project owner to release? |
You can, I can review and merge it at some point when I have time. |
When using SQLAlchemy 1.2.2 with Flask-WTF 0.14.2, using a QuerySelectField, Flask-WTF raises "ValueError: too many values to unpack" in
wtforms/ext/sqlalchemy/fields.py
line 189, inget_pk_from_identity
. It appears that SQLAlchemy 1.2 and later returns a third member from that call, and the library only expects two. Here's separate project's PR about the issue, and whose fix may be worth considering:wtforms/wtforms-sqlalchemy#10
I've put together a small Flask app demonstrating the bug here:
https://github.com/commandtab/flask-wtf-example
The text was updated successfully, but these errors were encountered: