Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Please remove the upper bound on Django

Open Beginner friendly
#714 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
django, python
Domain
build-system

Research direction

Open pyproject.toml and inspect the CRX dependency constraint and its adjacent comment. Remove the Django upper bound so it matches the stated Wagtail constraint, then verify that the dependency metadata permits Django 6.0 and that the existing supported-version checks remain unchanged.

Written by the indexing model from the issue text.

Description

Type: Bug
Describe the bug

Wagtail works like a charm with Django 6.0+ but I can’t install CRX because of that upper bound.
The comment in pyproject.toml is even misguiding:

dependencies = [
    ...
    "Django>=4.2,<6.0",  # should be the same as wagtail
]

The Wagtail’s pyproject.toml:

dependencies = [
    ...
    "Django>=4.2"
]

I see that CRX is tested against 5.2 and below, so it’s my responsibility to dare use it with Django 6.


Some opinion on the subject: https://iscinumpy.dev/post/bound-version-constraints/

Dominant language
Python
Stars
765
Forks
154
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coderedcorp/coderedcms

All issues in coderedcorp/coderedcms

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.