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 Sebastian.Noack
Recipients Sebastian.Noack, berker.peksag, ghaering, serhiy.storchaka
Date 2020-01-21.20:13:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1579637626.75.0.197981304003.issue39408@roundup.psfhosted.org>
In-reply-to
Content
Well, the stdlib already depends on a third-party library here, i.e. SQLite3. SQLCipher is a drop-in replacement for SQLite3 that adds support for encrypted databases. In order to use SQLCipher, I'd have to build the sqlite3 module against SQLCipher (instead of SQLite3). As it's a drop-in replacement, no further changes are required (unless rather than having SQLCipher bindings exposed as a separate module, we want enable it through an argument in sqlite3.connect).
History
Date User Action Args
2020-01-21 20:13:46Sebastian.Noacksetrecipients: + Sebastian.Noack, ghaering, berker.peksag, serhiy.storchaka
2020-01-21 20:13:46Sebastian.Noacksetmessageid: <1579637626.75.0.197981304003.issue39408@roundup.psfhosted.org>
2020-01-21 20:13:46Sebastian.Noacklinkissue39408 messages
2020-01-21 20:13:46Sebastian.Noackcreate