We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm working on new migrations for which I use a default value for a field and I get:
AddField with default value (new-db-field-with-default)
I have # pylint: disable=new-db-field-with-default in my source files but that doesn't seem to help, kiwitcms/Kiwi@20fed40 (second commit in the PR).
# pylint: disable=new-db-field-with-default
I thought this is a similar issue to #278 / #280 but as far as I can see we have @utils.check_messages() decorator here.
@utils.check_messages()
@carlio any ideas here ? I'm looking at the source but not seeing anything obvious. Will try debugging in the next few days.
pip freeze | grep pylint pylint==2.6.0 pylint-django==2.3.0 pylint-plugin-utils==0.6
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm working on new migrations for which I use a default value for a field and I get:
AddField with default value (new-db-field-with-default)
I have
# pylint: disable=new-db-field-with-default
in my source files but that doesn't seem to help, kiwitcms/Kiwi@20fed40 (second commit in the PR).I thought this is a similar issue to #278 / #280 but as far as I can see we have
@utils.check_messages()
decorator here.@carlio any ideas here ? I'm looking at the source but not seeing anything obvious. Will try debugging in the next few days.
The text was updated successfully, but these errors were encountered: