bpo-31746: Prevent segfaults with uninitialised sqlite3.Connection objects#27431
Conversation
|
Backport to 3.9 as well? |
Sorry, something went wrong.
|
Thanks @erlend-aasland for the PR, and @pablogsal for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10. |
Sorry, something went wrong.
|
Sorry, @erlend-aasland and @pablogsal, I could not cleanly backport this to |
Sorry, something went wrong.
|
Thanks @erlend-aasland for the PR, and @pablogsal for merging it 🌮🎉.. I'm working now to backport this PR to: 3.9. |
Sorry, something went wrong.
|
Sorry @erlend-aasland and @pablogsal, I had trouble checking out the |
Sorry, something went wrong.
|
Oh, seems that the backport party crashed :( @erlend-aasland can you do them manually? |
Sorry, something went wrong.
Yes, I was expecting it to fail. I'll fix it right away. Should we backport to 3.9 as well? |
Sorry, something went wrong.
|
@erlend-aasland apparently we have a buildbot failure: https://buildbot.python.org/all/#/builders/596/builds/703/ We may need to revert this meanwhile we understand what failed |
Sorry, something went wrong.
…alised (pythonGH-27431). (cherry picked from commit 7e311e4) Co-authored-by: Erlend Egeberg Aasland <erlend.aasland@innova.no>
|
Yes, please revert it. |
Sorry, something went wrong.
|
We are missing the 3.10 backport still |
Sorry, something went wrong.
Doh, I'll get to it after morning coffee :) |
Sorry, something went wrong.
…ialised (pythonGH-27431). (cherry picked from commit 7e311e4) Co-authored-by: Erlend Egeberg Aasland <erlend.aasland@innova.no>
Sync with main bco. pythonGH-27431
sqlite3.Connection.initializedwhen the connection objectis initialised
close()isolation_level[1] This may happen during connection init, so we cannot use
pysqlite_connection_commit, since it requires an initialisedconnection object. Previously, this was not a problem, since the
initialised flag was incorrectly set before the connection object was
initialised.
https://bugs.python.org/issue31746