Re: Python and sqlite versions

References	<m197l3$2r9$1@ger.gmane.org> <CAKJDb-P8LPvnX7YziANvmJ9g4sWV5Oh_mJ-N93LuEUZGcuG1MA@mail.gmail.com> <543830EF.8090008@bellissimmo.com> <CAKJDb-MnKgj=+qPJujDuPV9zn=42CFwRxzF2CLERcqRKRkpMRQ@mail.gmail.com> <m19g5o$evm$1@ger.gmane.org>
Date	2014-10-11 09:51 +1100
Subject	Re: Python and sqlite versions
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.14771.1412981472.18130.python-list@python.org> (permalink)

Show all headers | View raw

On Sat, Oct 11, 2014 at 7:39 AM, Simmo <steve@bellissimmo.com> wrote:
> On 10/10/2014 20:31, Zachary Ware wrote:
>> In that case (if I'm remembering correctly, I'm not on Windows at the
>> moment), you could probably back up C:\Python33\DLLs\sqlite3.dll
>> somewhere (just in case) and copy the sqlite3.dll you got with the
>> sqlite3 distribution into that folder, and Python should be happy to
>> use the newer version of sqlite3.
>>
>  That's got to be worth a punt.  What's the worst that can happen...
>

The worst? You could have nasty failures out of Python, segfaults,
stuff like that. In theory, it might even be able to corrupt your
database files, although I suspect not. So try it out with the memory
backend, make sure stuff's working, and make sure you did back up the
previous DLL (like he said to, but this is important enough to be
repeated).

Rolling back should be easy and safe. :)

ChrisA

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Python and sqlite versions Chris Angelico <rosuav@gmail.com> - 2014-10-11 09:51 +1100

csiph-web