[issue29230] Segfault in sqlite3

2017-01-16 Thread Ned Deily
Ned Deily added the comment: > I'm still trying to find a good way to get pyenv to recognize and use the > newer library Thanks for confirming that the problem was due to the version of sqlite3 in use. If you haven't already, suggest you open an issue on the pyenv project tracker or ask

[issue29230] Segfault in sqlite3

2017-01-16 Thread Daniel Fackrell
Daniel Fackrell added the comment: I was using versions of python from pyenv, but they may have been using the system version of sqlite3. I recreated the virtualenv using python 2.7.13 installed with Brew, and it doesn't crash. sqlite3.sqlite_version went from 3.8.10.2 to 3.16.2, which seems

[issue29230] Segfault in sqlite3

2017-01-10 Thread Ned Deily
Ned Deily added the comment: Thanks for the report. From a quick look at the macOS crash report, I'm guessing you are running with the Apple-supplied system Python 2.7 but with a virtualenv. In any case, the Apple-supplied libsqlite3 is in use and there are previously reported problems

[issue29230] Segfault in sqlite3

2017-01-10 Thread Daniel Fackrell
New submission from Daniel Fackrell: This crash occurs while running some unittests in one of our Django apps. It duplicates on all three versions I've tried (2.7.10, 2.7.12, and 2.7.13). I don't have a Python3-capable code to test against at present. It fails on my Mac OS system, and we