-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Django 3.1 #65
Conversation
When trying to install a celery version greater than 4 to a project, PipEnv cannot resolve the dependency since `setup.py` is set to <4.0 It is also clear that the package does not currently support Django 3.1 This commit addresses the following issues: - Updates the Tox/Travis config to allow for the testing of Django 3.1 with its supported Python versions (3.6, 3.7, and 3.8) See: https://docs.djangoproject.com/en/3.1/faq/install/ - Updates `setup.py` to have a constraint for celery of <5.0 - A couple of refactoring changes: - Replace nested if condition with a ternary operator (conditional expression) - Test params for truthiness instead of its length - Ran `isort` over the project and accepted its sorted imports - Updates `README.rst` to have an example Google Analytics code that is aligned with the Google docs and a user's actual tracking code. - Added `.vscode` to the `.gitignore` file to help VS Code contributors - Updated `CHANGELOG.rst` with the more major points of the change - Altered `Development Status` classifier to `5 - Production/Stable`. This was agreed in PR #62 by @rudigiesler I have NOT changed the version number within `setup.py`. I will let you do this upon build/release.
Hi, The build for the PR failed. The following is the pertinent part of the traceback from the Python 3.8 / Django 3.1 config:
Since then, I note on issue #64, @rudigiesler mentioned that version 2.2.5 is the lowest version supported by the package. Would you like me to submit another PR to supersede this one which updates the Thanks, Wayne |
@WayneLambert Looks good to me. I would add the higher Django version constraint to Happy for us to remove/cleanup testing on any versions that are no longer supported. Looking at the error, seems like I'm also happy to have |
Updates oversight from previous commit so that the `install_requires` config in `setup.py` now has a max version for Django of 3.2 Ref PR: #65
Hi @rudigiesler, I have updated the PR for that change. You're absolutely right - it was an oversight on my part. Of course, the automated build from the PR will obviously still fail. Yes, I'm more than happy for you guys to update the testing configurations to the supported versions. Yep, I did think the same with regards to Django Celery. Hopefully it doesn't cause any breakages if you just end up using celery directly. Good idea about adding isort to the CI. Thanks, Wayne |
Making the package compatible with Celery >4.0 will take more extensive effort, therefore this has been reversed back to its prior state. The objective is to make the package compatible with Django >=3.1 and <3.2 with a view to addressing Celery compatibility at a later stage. Ref: #65 See also: #64
Cleanup PR has been merged: #66 |
OK, that's great. Thanks. Following the revision for removing the attempt at making it compatible with Celery <5, the checks have now passed for the PR. Is there anything else required or can this be merged and a new release to PyPI? |
@WayneLambert Maybe just remove |
Remove entry for `Add support for Celery 4.x.x` PR: #65
Following my PR being merged in the Django Google Analytics app, a new release was made to PyPI. PR: praekeltfoundation/django-google-analytics#65
When trying to install a celery version greater than 4 to a project,
PipEnv cannot resolve the dependency since
setup.py
is set to <4.0It is also clear that the package does not currently support Django 3.1
This commit addresses the following issues:
with its supported Python versions (3.6, 3.7, and 3.8)
See: https://docs.djangoproject.com/en/3.1/faq/install/
setup.py
to have a constraint for celery of <5.0expression)
isort
over the project and accepted its sorted importsREADME.rst
to have an example Google Analytics code that isaligned with the Google docs and a user's actual tracking code.
.vscode
to the.gitignore
file to help VS Code contributorsCHANGELOG.rst
with the more major points of the changeDevelopment Status
classifier to5 - Production/Stable
.This was agreed in PR Update codebase for Django 3 and Python 3.8 #62 by @rudigiesler
I have NOT changed the version number within
setup.py
. I will let youdo this upon build/release.