delta/python-packages/astroid.git/astroid/objects.py, branch fix-python3-tests bitbucket.org: Obsolete (use python-packages/astroid-git Add a new SuperError exception subclass, SuperArgumentTypeError, which is raised when there's a problem with any argument of the super call (invalid types). 2015-05-29T13:58:58+00:00 Claudiu Popa cpopa@cloudbasesolutions.com 2015-05-29T13:58:58+00:00 5fdbef8c3617d2c53fd8c56081d40d985e8e406c 






Fail when calling Super.super_mro if the object-or-type is not the expected type.
2015-05-29T13:45:22+00:00

Claudiu Popa
cpopa@cloudbasesolutions.com

2015-05-29T13:45:22+00:00

94b27ec32afbce37083acf2c69256cf6ea8cb4fc












Remove unused import.
2015-05-28T19:00:11+00:00

Claudiu Popa
cpopa@cloudbasesolutions.com

2015-05-28T19:00:11+00:00

a1832df5727d24fbdb1ce362dec64bde619ca2f0












Update the rules for what descriptor is returned from a super(), depending on the accessed object.
2015-05-28T18:57:14+00:00

Claudiu Popa
cpopa@cloudbasesolutions.com

2015-05-28T18:57:14+00:00

adbf48b73e97905dc38583480fa663870c4ea1e2












Add a new *inference object* called Super
2015-05-28T09:10:00+00:00

Claudiu Popa
cpopa@cloudbasesolutions.com

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

237b6c4662cc0a14b1912748776e5effe92e2611

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.





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

Claudiu Popa
cpopa@cloudbasesolutions.com

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

d0ae4fa70b807324a6146ae63b5ff7789ed6c268












Add a new type of nodes, called *inference objects*.
2015-05-19T16:40:25+00:00

Claudiu Popa
cpopa@cloudbasesolutions.com

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

91529224bd4ad1a80065a76a9e077697b9ebecd0

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.





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.