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 ghaering
Recipients carloverre, ghaering, loewis
Date 2008-02-19.13:08:14
SpamBayes Score 0.10798428
Marked as misclassified No
Message-id <1203426496.92.0.210668722969.issue2139@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think pysqlite 2.3.2 is very buggy. Otherwise a lot more bug
reports about the pysqlite module would have arrived here. About
backporting fixes to 2.5.3, I'd have to look which ones are isolated and
I could then backport them.

As for SQLite, I'm always for just using the latest DLL and ship it with
Windows. But IMO now we should just ship whatever is in the release
candidate right now.

If the SQLite DLL proves to be a problem, users can always just install
their custom one over the one shipped with Python.
History
Date User Action Args
2008-02-19 13:08:17ghaeringsetspambayes_score: 0.107984 -> 0.10798428
recipients: + ghaering, loewis, carloverre
2008-02-19 13:08:16ghaeringsetspambayes_score: 0.107984 -> 0.107984
messageid: <1203426496.92.0.210668722969.issue2139@psf.upfronthosting.co.za>
2008-02-19 13:08:15ghaeringlinkissue2139 messages
2008-02-19 13:08:15ghaeringcreate