Upgrade Django version
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The current (3.0.3) version of Django requires psycopg2 <2.9.
https://stackoverflow.com/q/68024060/4107809
Python 3.11 does not work with these versions of psycopg2.
psycopg replaces psycopg2 starting in 4.2
is_ajax() call is deprecated in 3.1. See release notes
Postgres 9.6 support is dropped in Django 4.0
USE_L10N is discontinued on Django 5.0.
Maybe target LTS release 5.2. Django 6.0 requires python 3.12.
The default primary key behavior changes in 3.2, from 32 bits to 64 bits.
https://docs.djangoproject.com/en/6.0/releases/3.2/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Django release notes and inventory the project’s uses of is_ajax(), USE_L10N, primary keys, and PostgreSQL. Confirm the target Django release and Python/PostgreSQL compatibility before addressing each migration issue; done means the upgrade target is agreed and the application works with its supported dependency versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, postgresql, python
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100