Closed MacLake closed 2 years ago
I guess the requirement for 'Django>=1.11,<=3.2'
was set by mistake, as it matches 3.2, but not the bug fix and security releases 3.2.* from 3.2.1 on.
We were also bitten by this, please consider merging this PR. :pray:
Bumping this and adding my voice to the chorus - please consider merging this, so those of us looking to move to Django 3.2 don't have to maintain a custom fork of this just for the dependency issue. Thanks!
Thank you! Any chance of releasing a new point release to PyPi, please? :pray:
@mbi I'm afraid I don't have access to release.
Hi, regarding the release - please join #release-management on Slack where we can discuss next steps with our contributor team. The django CMS project is completely community driven. For this reason, we all need to work together to find a solution. Pypi access is currently only in the hands of a handful of people (for obvious reasons) - but except for django-cms, the releases for other packages are not really organized at the moment. We need to change that.
We had <=3.2, which doesn’t work for >=3.2.1. <3.3 works for 3.2.*.