-
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
AttributeError: 'NoneType' object has no attribute 'pattern' #108
Comments
What version of Try to downgrade the |
I try to downgrade pylint to a early version but I encounter other problems. Thanks for the help. Feel free to close this issue. |
Downgrading to pylint 1.7.5 fixes it for me.
Python 3.6.3 installed via Homebrew. |
I have the same issue. |
@christianmlong Thank you somuch! |
While downgrading to pylint 1.7.5 temporarily fixes this issue, it does present other errors (like pylint-dev/pylint#1609 which are fixed with pylint 1.8+ I believe). I have a project that is using Django 2.0 and I've been using pylint-django with it. Some days ago I configured Travis CI and today when I added pylint to the command list I found this very issue. 😉 Build log can be found here: https://travis-ci.org/renatoliveira/notto/builds/318305203 Using:
When Pylint is upgraded to 1.8.1, I get the AttributeError mentioned by @rgaiacs as well. |
seems there was some breaking changes with setup
using pylint 1.7
|
See pylint-dev/pylint-django#108 Signed-off-by: Michal Čihař <[email protected]>
When can we expect a fix for this? Had to update pylint and just got caught by this |
I'm also affected by this issue. Going back to 1.7.5 causes other issues as mentioned above. |
This updates the following packages: - faker from 0.8.7 to 0.8.8 - django-extensions from 1.9.7 to 1.9.8 - flake8-commas from 0.4.3 to 1.0.0 - flake8-quotes from 0.12.0 to 0.13.0 - setuptools from 38.2.3 to 38.4.0 To avoid a bug in pylint-django (caused by changes in the new minor releases of pylint and astroid), pylint and astroid versions are pinned to the last safe versions. pylint-dev/pylint-django#108 Finally, all versions of Django 2.0 have the alpha version removed, creating ranges for only stable versions. Django 2.0 is used when building documentation instead of Django 1.11.
if anyone else is struggling with this, jambonrose pointed me in the right direction with his commit (jambonrose/django-improved-user@4efdea7)
You'll need to pin/downgrade both to have a working environment:
|
for compatiblity with pylint 1.8+ Fixes pylint-dev#108 Original PR: pylint-dev#109 Obsolete PR: pylint-dev#111
for compatiblity with pylint 1.8+ Fixes pylint-dev#108 Original PR: pylint-dev#109 Obsolete PR: pylint-dev#111
for compatiblity with pylint 1.8+ Fixes pylint-dev#108 Original PR: pylint-dev#109 Obsolete PR: pylint-dev#111
for compatiblity with pylint 1.8+ Fixes pylint-dev#108 Original PR: pylint-dev#109 Obsolete PR: pylint-dev#111
for compatiblity with pylint 1.8+ Fixes pylint-dev#108 Original PR: pylint-dev#109 Obsolete PR: pylint-dev#111
@atodorov : Awesome! Any idea when the next release will come? |
@hajotka very soon. Maybe even today. |
@atodorov Hello, the issue seem to have come back in 0.11 with Pylint 1.8.4 or even 1.8.2. Version 0.10.1 is fine. |
@ecstaticpeon open a new issue for that with the code that reproduces it. |
@atodorov Actually it looks like it was something else in my environment. Sorry for the false alarm! |
Travis CI is falling for me in another project because of
Any suggestions of what can be causing it?
The text was updated successfully, but these errors were encountered: