Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #78976 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2014-10-11 09:51 +1100 |
| Last post | 2014-10-11 09:51 +1100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Python and sqlite versions Chris Angelico <rosuav@gmail.com> - 2014-10-11 09:51 +1100
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2014-10-11 09:51 +1100 |
| Subject | Re: Python and sqlite versions |
| Message-ID | <mailman.14771.1412981472.18130.python-list@python.org> |
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 top | Article view | comp.lang.python
csiph-web