How to override an old sqlite3 module with pysqlite3 in django settings.py

settings.py

# ⚠️ USE AT YOUR OWN RISK
# first: pip install pysqlite3-binary
# then in settings.py:

# these three lines swap the stdlib sqlite3 lib with the pysqlite3 package
__import__('pysqlite3')
import sys
sys.modules['sqlite3'] = sys.modules.pop('pysqlite3')

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.sqlite3',
        'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
    }
}

@tyler-suard-parker, thanks to your solution, I've got it working with an Azure Web App. To fix the writing to the file system, I added the mkdir line to an already existing startup.sh file (since my web app uses Quart and hypercorn instead of gunicorn)

mkdir -p antenv/lib/python3.11/site-packages/google/colab
python -m hypercorn --bind=0.0.0.0 app:app;

(If you're using gunicorn it'd look something like

mkdir -p antenv/lib/python3.11/site-packages/google/colab
gunicorn --bind=0.0.0.0 --timeout 600 app:app

)

Then point your app's startup command to the file, in Settings > Configuration > Startup Command = ./startup.sh

You do not need to modify anything. To bypass the Colab check, you can create an empty folder google/colab in the site packages folder. That way on the Chroma __init__.py when it tries to do the import google.colab check it will pass, and thus replace sqlite3 with pysqlite3

This worked for me!!

You do not need to modify anything. To bypass the Colab check, you can create an empty folder google/colab in the site packages folder. That way on the Chroma __init__.py when it tries to do the import google.colab check it will pass, and thus replace sqlite3 with pysqlite3

This worked for me!!

worked for me too

What do we have to do, if we are deploying on streamlit?

Hey did you solve this issue ?

Hey, so I was able to bypass this issue by just adding pysqlite3-binary to requirements.txt

Did not have to add any versioning, or other code.

Hey, were you deploy on the cloud, I wanted to deploy on streamlit, but error persist even after adding it to the requirement file

same problem here in streamlit community cloud

raise RuntimeError(
RuntimeError: Your system has an unsupported version of sqlite3. Chroma requires sqlite3 >= 3.35.0.

how to solve this issue?

It seems like they know the issue. It just matters on them upgrading the Debian OS from bullseye to bookworm https://discuss.streamlit.io/t/debian-11-eol/80690/7

This seemed to work for me:

1. Download the Latest SQLite Source:
   wget https://www.sqlite.org/2023/sqlite-autoconf-3430100.tar.gz

2. Extract the Downloaded File:
   tar -xvf sqlite-autoconf-3430100.tar.gz
   cd sqlite-autoconf-3430100

3. Build and Install SQLite:
   ./configure
   make
   sudo make install

4. Verify the Installation:
   After installation, confirm that the new version is available:
   sqlite3 --version

5. Verify in Python:
   Ensure that Python picks up the updated SQLite version:

python -c "import sqlite3; print(sqlite3.sqlite_version)"

thanks, worked for me.

import('pysqlite3')
import sys
sys.modules['sqlite3'] = sys.modules.pop('pysqlite3')

Worked perfectly for me too.

This gives the error
NameError: name 'sqlite3' is not defined

import('pysqlite3')
import sys
sys.modules['sqlite3'] = sys.modules.pop('pysqlite3')