Message 308024 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	mdk
Recipients	lelit, mdk
Date	2017-12-11.10:35:31
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
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 destroyed, which happen when no reference are kept on the connection, indifferently of a success or a failure of the connection. It's in Modules/_sqlite/connection.c

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 destroyed, which happen when no reference are kept on the connection, indifferently of a success or a failure of the connection.

It's in Modules/_sqlite/connection.c

History
Date	User	Action	Args
2017-12-11 10:35:31	mdk	set	recipients: + mdk, lelit
2017-12-11 10:35:31	mdk	set	messageid: <[email protected]>
2017-12-11 10:35:31	mdk	link	issue32274 messages
2017-12-11 10:35:31	mdk	create