Start testing on Django v5.1

[cclauss]

Test the pre-release version of Django v5.1 scheduled to be released in August 2024.

• https://docs.djangoproject.com/en/dev/releases/5.1

---

Why does upgrading Django v5.0 --> v5.1rc1 downgrade these?

• This is a repeat on Django v5.1 of Release Django 5.0 compatible package to PyPI #680 (comment)

django-celery-beat: 2.6.0 --> 2.1.0
django-timezone-field: 7.0.0 --> 4.2.3

% diff django-celery-beat-on-dj50/requirements.txt  \
       django-celery-beat-on-dj51rc1/requirements.txt

9,12c9,11
< cron-descriptor==1.4.3
< Django==5.0.6
< django-celery-beat==2.6.0
< django-timezone-field==7.0
---
> Django==5.1rc1
> django-celery-beat==2.1.0
> django-timezone-field==4.2.3
16a16
> pytz==2024.1

---

mkdir django-celery-beat-on-dj50 \
 && cd django-celery-beat-on-dj50 \
 && python3.12 -m venv venv \
 && source venv/bin/activate \
 && pip install --upgrade pip \
 && pip install Django==5.0.6 django-celery-beat \
 && pip freeze > requirements.txt \
 && cd .. \
 && mkdir django-celery-beat-on-dj51rc1 \
 && cd django-celery-beat-on-dj51rc1 \
 && python3.12 -m venv venv \
 && source venv/bin/activate \
 && pip install --upgrade pip \
 && pip install Django==5.1rc1 django-celery-beat \
 && pip freeze > requirements.txt \
 && cd .. \
 && diff django-celery-beat-on-dj50/requirements.txt  \
         django-celery-beat-on-dj51rc1/requirements.txt \
 && rm -fr django-celery-beat-on-dj5*

[Nusnus]

Approved - check out my comment though

[cclauss]

@Nusnus Any thoughts on the downgrades above?

[Nusnus]

@Nusnus Any thoughts on the downgrades above?

If I had to guess I’d say they just “didn’t get to it yet” in terms of upgrading the dependencies.
I think it’s worth creating an issue with Django to ask about it and avoid merging this PR until we have some official answers.

[Nusnus]

@Nusnus Any thoughts on the downgrades above?

If I had to guess I’d say they just “didn’t get to it yet” in terms of upgrading the dependencies. I think it’s worth creating an issue with Django to ask about it and avoid merging this PR until we have some official answers.

But I think they’ll just answer you with “oh thanks for letting us know, fixed in PR 1234”, or at least I hope so haha

[Mogost]

@cclauss You are doing a strange thing here.

mkdir django-celery-beat-on-dj50 \
 && cd django-celery-beat-on-dj50 \
 && python3.12 -m venv venv \
 && source venv/bin/activate \
 && pip install --upgrade pip \
 && pip install Django==5.0.6 django-celery-beat \
 && pip freeze > requirements.txt \
 && cd .. \
 && mkdir django-celery-beat-on-dj51b1 \
 && cd django-celery-beat-on-dj51b1 \
 && python3.12 -m venv venv \
 && source venv/bin/activate \
 && pip install --upgrade pip \
 && pip install Django==5.1b1 django-celery-beat \
 && pip freeze > requirements.txt \
 && cd .. \
 && diff django-celery-beat-on-dj50/requirements.txt  \
         django-celery-beat-on-dj51b1/requirements.txt \
 && rm -fr django-celery-beat-on-dj5*

How this is possible if you have an upper Django version limit in the released django-celery-beat?

pip install Django==5.1b1 django-celery-beat

Resolver just solved what it should do and picked the latest django-celery-beat version where there was no upper limit.

v2.1.0...v2.2.0#diff-18e078b1884440a7faf1b20b7f91c400c15aca08a74243935946983631259b80
There were no restrictions in 2.1.0 for Django.

pip install Django==5.1b1 django-celery-beat==2.6.0
Collecting Django==5.1b1
Collecting celery<6.0,>=5.2.3
Collecting django-timezone-field>=5.0
Collecting tzdata
Collecting python-crontab>=2.3.4
Collecting cron-descriptor>=1.2.32

ERROR: Cannot install Django==5.1b1 and django-celery-beat==2.6.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested Django==5.1b1
    django-celery-beat 2.6.0 depends on Django<5.1 and >=2.2

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

[cclauss]

You are doing a strange thing here.

😀

So you are saying that #756 was made but not released to PyPI and once that is done the downgrades will not happen?

• relaxed django upper version limit to 5.1 #756

[Mogost]

So you are saying that #756 was made but not released to PyPI and once that is done the downgrades will not happen?

Absolutely so.