fix: Add PostgreSQL support for Django 6.0 compatibility #182
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes the Django 6.0 compatibility issue by adding proper PostgreSQL support for tests and moving
psycopgto main dependencies.Problem
After upgrading to Django 6.0, Wagtail requires
django.contrib.postgresto be inINSTALLED_APPSwhen using PostgreSQL-specific features likeSearchVectorFieldandGinIndex. However, adding this toINSTALLED_APPScaused CI tests to fail because:django.contrib.postgresrequirespsycopgto be installedpsycopgwas only inrequirements/production.txtmain.txtanddev.txtModuleNotFoundError: No module named 'psycopg'Solution
1. Add PostgreSQL to CI Tests (
.github/workflows/test.yml)DATABASE_URLto use PostgreSQL in CI2. Conditional Database Configuration (
pythonie/pythonie/settings/tests.py)DATABASE_URLis set (CI)DATABASE_URLis not set (local development)3. Move psycopg to Main Dependencies
psycopg[binary]fromrequirements/production.intorequirements/main.indjango.contrib.postgresis now in baseINSTALLED_APPS, psycopg is a core dependencyChanges
Testing
Related Issues
Fixes the deployment error from Django 6.0 upgrade:
Checklist