[issue32274] Potential leak in pysqlite_connection_init()

Lele Gaifax added the comment: You are right, thank you. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue32274] Potential leak in pysqlite_connection_init()

Julien Palard added the comment: I don't see a leak here: as long as nobody keep a reference to each connection objects, pysqlite_connection_dealloc will be called and will call the sqlite3_close. In other words the sqlite3_close is called when the connection is

[issue32274] Potential leak in pysqlite_connection_init()

New submission from Lele Gaifax : The function calls ``sqlite3_open()`` that, if I understand its documentation correctly[#], returns a new connection object in all cases (that is, even on errors) with the only exception of "out of memory" (in which case it sets the