无root权限且不影响全局包，如何在Python3.6虚拟环境（venv）中升级SQLite版本？

Hey there! Let's break down your problem into two easy-to-follow solutions, since you either want to bypass the SQLite check entirely (since you don't plan to use it) or upgrade SQLite within your virtual environment without root access.

Solution 1: Bypass SQLite Version Check by Switching to Another Database #

Since you don't intend to use SQLite for your project, this is the simplest approach. Django only checks SQLite's version when you're using it as your database backend. Here's what to do:

• First, pick a database your team uses (like PostgreSQL or MySQL) and install the required driver in your virtual environment:
  • For PostgreSQL: Run pip install psycopg2-binary
  • For MySQL: Run pip install mysqlclient
• Open your project's settings.py file, find the DATABASES section, and replace the default SQLite configuration with your target database's details. It should look something like this (example for PostgreSQL):

  DATABASES = {
      'default': {
          'ENGINE': 'django.db.backends.postgresql',
          'NAME': 'your_database_name',
          'USER': 'your_db_username',
          'PASSWORD': 'your_db_password',
          'HOST': 'db_host',
          'PORT': '5432',
      }
  }
  

  Ask your team for the correct connection info if you don't have it!
• Important: Django Admin requires database tables to work, so you need to apply all migrations (including Admin's) to your new database. Run:

  python manage.py migrate
  

• Now start your development server with python manage.py runserver—it won't check SQLite's version anymore because you're using a different database backend.

Solution 2: Upgrade SQLite Within Your Virtual Environment #

If you need to use SQLite temporarily (or just want to fix the version check without switching databases), you can compile and install a newer SQLite version directly into your venv (no root needed):

1. Activate your virtual environment first:
   • Linux/macOS: source venv/bin/activate
   • Windows: venv\Scripts\activate
2. Download the latest stable SQLite source code and extract it. For example, if you downloaded sqlite-autoconf-3400000.tar.gz:

   tar xzf sqlite-autoconf-3400000.tar.gz
   cd sqlite-autoconf-3400000
   

3. Compile and install SQLite into your virtual environment's directory (so it doesn't affect other users):

   ./configure --prefix=$VIRTUAL_ENV && make && make install
   

4. Tell your virtual environment to use this new SQLite version instead of the system's old one:
   • Linux/macOS: Run this in your terminal (after activating venv):

     export LD_LIBRARY_PATH=$VIRTUAL_ENV/lib:$LD_LIBRARY_PATH
     

     To make this permanent for your venv, add this line to venv/bin/activate so it runs every time you activate the environment.
   • Windows: You'll need to add the venv\Lib folder to your PATH environment variable temporarily or permanently for the venv.
5. Verify the upgrade worked:

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

   You should see the newer version number you installed.
6. Now start your Django dev server as usual—it should recognize the updated SQLite version and run without issues.

Quick Note for Beginners #

• When switching databases, always make sure you run python manage.py migrate—this creates all the necessary tables (including those for Django Admin) in your new database. Skipping this will break the Admin interface.
• If you go the SQLite upgrade route, remember that the LD_LIBRARY_PATH change only applies to your current terminal session unless you add it to the activate script.

内容的提问来源于stack exchange，提问作者raghavj