-
Notifications
You must be signed in to change notification settings - Fork 17
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
Delete deprecated argument #42
Conversation
@heller166 Thanks for contributing, Can you please write this code in a backward compatible way so that it doesn't break for old version of Django and works for the newer versions too? |
I'm not sure that I can do that now that. I was trying to avoid getting a
|
Codecov Report
@@ Coverage Diff @@
## master #42 +/- ##
=======================================
Coverage 90.25% 90.25%
=======================================
Files 3 3
Lines 154 154
Branches 26 26
=======================================
Hits 139 139
Misses 10 10
Partials 5 5
Continue to review full report at Codecov.
|
@heller166 You did't had to close your pull request. Check this code, how we can fix some deprecation warnings or errors using this conditionals, and also this:
|
@vinitkumar thanks for the suggestion. I implemented a solution, let me know what you think. I tried to come up with some way to test this but it seemed a bit more trouble than its worth. |
djangocms_attributes_field/fields.py
Outdated
@@ -10,6 +10,8 @@ | |||
from django.utils.translation import ugettext as _ | |||
from django.utils.translation import ugettext_lazy | |||
|
|||
from cms.utils.compat import DJANGO_2_2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file doesn't exists in the repo, just copy the same logic into a utils file and use that to import and this should be fine.
@vinitkumar looks like there has been some work since your comments so could you review again? |
@fsbraun The change looks good here. Should we merge it? |
@vinitkumar could merge it so the author gets their contribution in and then extend it because the support brought in should be the standard now with nobody using 2.2 |
@marksweb Roger that. |
Support for context argument was removed in Django 3.0