delta/python-packages/astroid.git/ChangeLog, branch fix-python3-tests

Add a new inference object called Super

2015-05-28T09:10:00+00:00

This patch also adds support for understanding super calls.
astroid understands the zero-argument form of super, specific to
Python 3, where the interpreter fills itself the arguments of the call. Also, we
are understanding the 2-argument form of super, both for bounded lookups
(super(X, instance)) as well as for unbounded lookups (super(X, Y)),
having as well support for validating that the object-or-type is a subtype
of the first argument. The unbounded form of super (one argument) is not
understood, since it's useless in practice and should be removed from
Python's specification. Closes issue #89.

Specify that inference objects can be found in the AST tree, but only after inference.

2015-05-19T17:43:45+00:00

Add a new type of nodes, called inference objects.

2015-05-19T16:40:25+00:00

Inference objects are similar with AST nodes, but they can be obtained
only after inference, so they can't be found inside the AST tree.
Their purpose is to handle at astroid level some operations which can't
be handled when using brain transforms. For instance, the first object
added is FrozenSet, which can be manipulated at astroid's level
(inferred, itered etc). Code such as this 'frozenset((1,2))'
will not return an Instance of frozenset, without having access to its
content, but a new objects.FrozenSet, which can be used just as a nodes.Set.

Add support for understanding context managers created with contextlib.contextmanager.

2015-05-09T16:27:13+00:00

Add basic support for understanding context managers.

2015-05-09T12:58:31+00:00

Currently, there's no way to understand whatever __enter__ returns in a
context manager and what it is binded using the ``as`` keyword. With these changes,
we can understand ``bar`` in ``with foo() as bar``, which will be the result of __enter__.
There's no support for contextlib.contextmanager yet.

Class.has_dynamic_getattr doesn't return True for special methods which aren't implemented in pure Python.

2015-05-07T10:52:36+00:00

Since most likely the methods were coming from a live object, this implies
that all of them will have __getattr__ and __getattribute__ present and it
is wrong to consider that those methods were actually implemented
(the descriptors will be there, not necessarily implying that the function
is user implemented).

Classes aren't marked as interfaces anymore, in the `type` attribute.

2015-05-05T08:37:51+00:00

Add two new exceptions for handling MRO error cases.

2015-05-03T06:21:04+00:00

DuplicateBasesError is emitted when duplicate bases are found in a class,
InconsistentMroError is raised when the method resolution is determined
to be inconsistent. They share a common class, MroError, which
is a subclass of ResolveError, meaning that this change is backwards compatible.

Ensure that generated enum values have the correct base classes

2015-05-01T08:44:12+00:00

Enum values should share the same base classes as their defining class.
If this is not the case it may lead to wrong inference results when an
enum member is used - e.g. for the following snippet:

class X(enum.IntEnum):
    one = 1

print([1, 2][X.one])

pylint will detect a "invalid-sequence-index" error as the __index__
method of X.one is not detected.

Expose a implicit_metaclass() method in Class.

2015-04-24T21:29:31+00:00

This will return a builtins.type instance for newstyle classes, otherwise it will
return None.