Pin pylint-django to latest version 0.7.2

[pyup-bot]

pylint-django is not pinned to a specific version.

I'm pinning it to the latest version 0.7.2 for now.

These links might come in handy: PyPI | Changelog | Repo

Changelog

0.7.2

• 76 Better handling of mongoengine querysetmanager
• 73 (72)[https://github.com/ImportError: No module named pylint_django pylint-dev/pylint-django#72] Make package zip safe to help fix some path problems
• 68 Suppressed invalid constant warning for "app_name" in urls.py
• 67 Fix view.args and view.kwargs
• 66 accessing _meta no longer causes a protected-access warning as this is a public API as of Django 1.8
• 65 Add support of mongoengine module.
• 59 Silence old-style-class for widget Meta

0.7.1

• 52 - Fixed stupid mistake when using versioninfo

0.7

• 51 - Fixed compatibility with pylint 1.5 / astroid 1.4.1

0.6.1

• 43 - Foreign key ID access (somefk_id) does not raise an 'attribute not found' warning
• 31 - Support for custom model managers (thanks smirolo)
• 48 - Added support for django-restframework (thanks mbertolacci)

0.6

• Pylint 1.4 dropped support for Python 2.6, therefore a constraint is added that pylint-django will only work with Python2.6 if pylint<=1.3 is installed
• 40 - pylint 1.4 warned about View and Model classes not having enough public methods; this is suppressed
• 37 - fixed an infinite loop when using astroid 1.3.3+
• 36 - no longer warning about lack of __unicode__ method on abstract model classes
• PR 34 - prevent warning about use of super() on ModelManager classes

0.5.5

• PR 27 - better ForeignKey transforms, which now work when of the form othermodule.ModelClass. This also fixes a problem where an inferred type would be _Yes and pylint would fail
• PR 28 - better knowledge of ManyToManyField classes

0.5.4

• Improved resiliance to inference failure when Django types cannot be inferred (which can happen if Django is not on the system path

0.5.3

• Issue 25 Fixing cases where a module defines get as a method

0.5.2

• Fixed a problem where type inference could get into an infinite loop

0.5.1

• Removed usage of a Django object, as importing it caused Django to try to configure itself and thus throw an ImproperlyConfigured exception.

0.5

• Issue 7
  Improved handling of Django model fields
• Issue 10
  No warning about missing unicode if the Django python3/2 compatability tools are used
• Issue 11
  Improved handling of Django form fields
• Issue 12
  Improved handling of Django ImageField and FileField objects
• Issue 14
  Models which do not define unicode but whose parents do now have a new error (W5103)
  instead of incorrectly warning about no unicode being present.
• Issue 21
  ForeignKey and OneToOneField fields on models are replaced with instance of the type
  they refer to in the AST, which allows pylint to generate correct warnings about attributes
  they may or may not have.

0.3

New Features

• Python3 is now supported

Bugfixes

• __unicode__ warning on models does not appear in Python3

0.2

New Features

• Pylint now recognises BaseForm as an ancestor of Form and subclasses
• Improved Form support

Bugfixes

• Issue 2 - a subclass of a Model or Form also has
  warnings about a Meta class suppressed.
• Issue 3 - Form and ModelForm subclasses no longer
  warn about Meta classes.

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖