Release Django 5.0 compatible package to PyPI

[nijel]

Summary:

Include a brief description of the problem here, and fill out the version info below.

• Celery Version: 5.3.5
• Celery-Beat Version: 2.5.0

Exact steps to reproduce the issue:

1. Try to install Django 5.0a1 with django-celery-beat
2. django-celery-beat 2.5.0 has requirement Django<5.0,>=2.2, but you have django 5.0a1.

Detailed information

See https://docs.djangoproject.com/en/dev/releases/5.0/ for release notes.

[auvipy]

• Update runtime.txt to include Django 5.0 #681

[yanivtoledano]

@auvipy - is there a timeline for the next release (with 5.0 support)?

[auvipy]

Hopefully early next week.

[kozlek]

Hi 👋

Based on what I understood, Django 5.0 support was simply a matter of relaxing the dependency constraints.
I'm not challenging the fact we have a dependency constraint with an upper bound.

The patch was made on the Sep 19, which is the release date of the first Django 5.0 alpha. This is an achievement: we managed to add support for the new Django release very early in the development process 🥳

However, 2 months later and 4 days after the final Django release, users are still not able to use it (or even test it easily) because we failed to release the working code we produced 2 months ago 😕

Far from judging (I've done manual releases myself for some time so I know how time consuming it is 😉), what can we do to help you @auvipy to ease the release process of this version and the following ones?

I'll be happy to look into a CI pipeline to provide an automated release if you are okay for it, but if you prefer to do it manually tell us if you need new maintainers for reviewing PRs or doing issues triage 🙂

[cclauss]

% python3.12 -m venv .venv
% source .venv/bin/activate
% pip install --upgrade pip
% pip install django==5.0 django-celery-beat==2.5.0 --> Failure
% pip install django==5.0 django-celery-beat --> Success but with

• django-celery-beat downgraded from 2.5.0 --> v2.1.0 and
• django-timezone-field downgraded from v6.1.0--> v4.2.3

Please release a new version to PyPI.

[kozlek]

I can't afford to further delay my Django 5.0 upgrade as I have planned features that depend on the new version capabilities.
As a workaround, I released a custom build of django-celery-beat on PyPi under another name.

As I don't expected anyone to trust my build, here are the steps I used to build and upload it if someone needs to do it for himself.
You need a PyPi account to do so, and my instructions require pipx, pyenv and a GNU version of sed.

# install twine to upload package to PyPi
pipx install twine

# install latest version of python (not mandatory) and enable it
pyenv install 3.12.1
pyenv virtualenv 3.12.1 dev
pyenv shell dev
pip install setuptools wheel # python 3.12.0+ does not install them by default

# get source code
git clone git@github.com:celery/django-celery-beat.git
cd django-celery-beat

# rename the package (replace custom by what you want)
sed -i 's/django-celery-beat/django-celery-beat-custom/g' setup.py 

# build the package
python setup.py sdist bdist_wheel

# upload to pypi
twine upload dist/*

[cclauss]

Were you able to get the tests to pass on Py3.12 and Dj5.0?

[kozlek]

Launching tox with the latest commit of the master branch using tox -e py312 installs Django 5.0 and reports 1 failure.

I choose to ignore it because it's related to the removal of django.utils.timezone.utc alias and it only affects systems running with USE_TZ=False which is not my case.

[kozlek]

It's quite easy to fix, as we simply need to use datetime.timezone.utc here instead, as we already do here.

However, we might also want to fix in the same time warnings regarding the deprecation of datetime.utcnow(), as I did for djangorestframework-simplejwt: jazzband/djangorestframework-simplejwt#765

IMHO, we should simply get rid of old python / django versions, remove support for USE_TZ=False and native datetime.
It would simplify library code a lot and it seems to be the direction taken by both Django and Python.

[cclauss]

• Django v5.0: django.utils.timezone.utc alias --> datetime.timezone.utc #703

.utcnow() is a Python 3.13 thing but upstream groundwork is in progress... celery/celery#8726

[chirag-jn]

Is there an ETA for django 5 support? I see that there's work in progress but I am eagerly waiting for the release.