Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==1.5.3
->==1.6.6
Release Notes
PyCQA/astroid
v1.6.6
Compare Source
v1.6.5
Compare Source
v1.6.4
Compare Source
v1.6.3
Compare Source
v1.6.2
Compare Source
v1.6.1
Compare Source
v1.6.0
Compare Source
============================
Release Date: 2017-12-15
When verifying duplicates classes in MRO, ignore on-the-fly generated classes
Close PyCQA/pylint#1706
Add brain tip for attrs library to prevent unsupported-assignment-operation false positives
Close PYCQA/pylint#1698
file_stream was removed, since it was deprecated for three releases
Instead one should use the .stream() method.
Vast improvements to numpy support
Add brain tips for curses
Close PyCQA/pylint#1703
Add brain tips for UUID.int
Close PyCQA/pylint#961
The result of using object.new as class decorator is correctly inferred as instance
Close #172
Enums created with functional syntax are now iterable
Enums created with functional syntax are now subscriptable
Don't crash when getting the string representation of BadUnaryOperationMessage
In some cases, when the operand does not have a .name attribute,
getting the string representation of a BadUnaryOperationMessage leads
to a crash.
Close PyCQA/pylint#1563
Don't raise DuplicateBaseError when classes at different locations are used
For instance, one can implement a namedtuple base class, which gets reused
on a class with the same name later on in the file. Until now, we considered
these two classes as being the same, because they shared the name, but in fact
they are different, being created at different locations and through different
means.
Close PyCQA/pylint#1458
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.