4 ms·
It would have to be the other way around or be a (possibly major) breaking change. Just execute() with strings is already standard python that all the framework
by Izkata 2y ago
It would have to be the other way around or be a (possibly major) breaking change. Just execute() with strings is already standard python that all the frameworks build on top of, not to mention tutorials:
https://docs.python.org/3/library/sqlite3.html https://docs.python.org/3/library/sqlite3.html
https://www.psycopg.org/docs/cursor.html https://www.psycopg.org/docs/cursor.html
https://dev.mysql.com/doc/connector-python/en/connector-python-api-mysqlcursor-execute.html https://dev.mysql.com/doc/connector-python/en/connector-pyth...
- dragonwriter 2y ago> It would have to be the other way around or be a (possibly major) breaking change. If it is going to reject the currently-accepted unsafe usage, its going to be a major breaking change in any case, so I don't see the problem. I mean, if you are lamenting it can't reject the currently-accepted SQL-interpolated-via-f-string because it can't distinguish it by type from plain strings with no interpolation, you are already saying that you want a major breaking change but are upset because the particular implementation you want is not possible. So you can't turn around and dismiss an alternative solution because it would be a major breaking change, that's what was asked for!