-
-
Notifications
You must be signed in to change notification settings - Fork 31k
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
[Doc] sqlite3 Cursor.execute() return value is unspecified #90923
Comments
In the documentation of the sqlite3 module, the return value for Connection.execute() is told to be the Cursor that was implicitly created, but nothing is said about the return value/type when using Cursor.execute(). |
Quoting the docs:
There is already a backlink (or back reference) to the Connection.cursor() method, which again has a backlink to the Cursor class. What would you suggest to make things clearer? How about the following rewording: "[...] and returns the newly created cursor object". (IMO this is too verbose; I'm fine with the current docs.) |
After re-reading the current docs, I think a rewording might be helpful. I'll see if I can make things a little bit clearer. |
- Drop 'nonstandard'; it does not add any value - Try to be more concise - Make return value a little more explicit
- Drop 'nonstandard'; it does not add any value - Try to be more concise - Make return value a little more explicit
) - Drop 'nonstandard'; it does not add any value - Try to be more concise - Make return value a little more explicit (cherry picked from commit 017f07a) Co-authored-by: Erlend Egeberg Aasland <[email protected]>
- Drop 'nonstandard'; it does not add any value - Try to be more concise - Make return value a little more explicit (cherry picked from commit 017f07a) Co-authored-by: Erlend Egeberg Aasland <[email protected]>
- Drop 'nonstandard'; it does not add any value - Try to be more concise - Make return value a little more explicit (cherry picked from commit 017f07a) Co-authored-by: Erlend Egeberg Aasland <[email protected]>
) - Drop 'nonstandard'; it does not add any value - Try to be more concise - Make return value a little more explicit (cherry picked from commit 017f07a) Co-authored-by: Erlend Egeberg Aasland <[email protected]>
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: