[issue34695] sqlite3: Cache.get() crashes if Cache.__init__() was not called

Berker Peksag added the comment: Thanks for the report and for the patch! This is a duplicate of issue 31734. The Cache class is an implementation detail and it has no use of outside of the sqlite3 implementation as you already said. For option 3, there is an open issue: #30262. IMO, the

[issue34695] sqlite3: Cache.get() crashes if Cache.__init__() was not called

Change by Berker Peksag : -- stage: patch review -> resolved ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34695] sqlite3: Cache.get() crashes if Cache.__init__() was not called

Serhiy Storchaka added the comment: This is a duplicate of issue31734. -- resolution: -> duplicate stage: patch review -> superseder: -> crash or SystemError in sqlite3.Cache in case it is uninitialized or partially initialized ___ Python

[issue34695] sqlite3: Cache.get() crashes if Cache.__init__() was not called

Change by Alexey Izbyshev : -- keywords: +patch pull_requests: +8754 stage: -> patch review ___ Python tracker ___ ___

[issue34695] sqlite3: Cache.get() crashes if Cache.__init__() was not called

New submission from Alexey Izbyshev : sqlite3.Cache allows users to create uninitialized instances because it relies on __init__() instead of __new__() for initialization, which can be skipped. Cache.get() crashes if called on an uninitialized instance: >>> from sqlite3 import Cache >>>