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 schlamar
Recipients BreamoreBoy, benjamin.peterson, ghaering, ned.deily, pitrou, schlamar, steve.dower, zach.ware
Date 2014-10-15.15:42:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yes, but this is no practical solution. Telling *all* my clients to update the sqlite3.dll after *every* Python update is just not feasible and will just not work out in practice. 

What would be the required steps to update the *.dll in the build? Just update the external.bat to fetch another version or I am missing something? 

I would suggest synchronizing it with Python 3, which means SQLite Or what do you think?
Date User Action Args
2014-10-15 15:42:34schlamarsetrecipients: + schlamar, ghaering, pitrou, benjamin.peterson, ned.deily, BreamoreBoy, zach.ware, steve.dower
2014-10-15 15:42:34schlamarsetmessageid: <>
2014-10-15 15:42:34schlamarlinkissue19450 messages
2014-10-15 15:42:34schlamarcreate