-
Notifications
You must be signed in to change notification settings - Fork 117
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
Merge updated fork #113
Merge updated fork #113
Conversation
this mimics more closely what pylint does for their own tests and doesn't rely on deprecated functionality. Fixes pylint-dev#107 and pylint-dev#97 Obsoletes pylint-dev#98
since we're testing with latest Django versions this is now required for all ForeignKey fields
the plugin should be able to suppress these kinds of errors for model classes and also for Meta classes so no need to disable them explicitly.
also remove couple of suppressions b/c these class checks are already handled by the check for meta class and they don't seem to have any effect
this was previously skipped but since we don't test on older versions we can explicitly add it again.
the latest version of pylint expects the error messages in slightly different format.
for compatiblity with pylint 1.8+ Fixes pylint-dev#108 Original PR: pylint-dev#109 Obsolete PR: pylint-dev#111
Added suppressions for [DjangoModelFactory](http://factoryboy.readthedocs.io/en/2.9.2/orms.html#the-djangomodelfactory-subclass). Original PR: pylint-dev#103
Checks that Pylint does not complain about django lazy proxy when using ugettext_lazy
Fix E1101:Instance of '__proxy__' has no 'format' member' when using .format() on a ugettext_lazy translation NOTE: merged with modifications. Instead of returning str, returns '' Fixes pylint-dev#80 Origina PR: pylint-dev#100
Original PR: pylint-dev#99 Fixes pylint-dev#95
Original PR: pylint-dev#92
NOTE: merged with modifications: - resolved conflicts - updated where test files are on disk Original PR: pylint-dev#84
This all looks good to me! Two comments - first, makes sense to wait for @colinhowe to have a look and also see what his changes are, may as well merge at the same time. Second - it'd probably be good to have some kind of deprecation or warning maybe in |
@carlio I can add the deprecation warning in a separate commit before we release 0.8. I have only removed testing for Python 2, mostly because I didn't have the time to deal with fixing the Python 2 tests. I have not modified the code to remove anything related to Py2 so everything will still work. And we can make version 0.8.0 the last that will support Py2, then declare this project Py3 only and move on. |
Oh I understand that completely! Sounds all good to me. |
I'm happy with all of this. My changes have made it in already via the work that @atodorov has done |
Let's do it! I'll let you push the button to make sure permissions are set up right, let me know if there are any problems |
Changes:
TODO: will remove custom naming and versioning coming from the fork and let you know when this is ready to merge and review.