New submission from Matthias Bussonnier: The `ast.Call/_ast.Call` signature, changed on May 5th (https://hg.python.org/cpython/rev/95886) which causes some error in package using ast (https://bitbucket.org/pytest-dev/pytest/issue/744/pytest-assert-rewriting-broken-with-python#). There does not seem to be any docs in the what's new about the change, though http://bugs.python.org/issue24136 is suppose to track some docs change, so not complaining about that.
Could `ast` shims the old signature and raise a warning until 3.6, to give some time for package to adapt ? ---------- components: Devguide messages: 243427 nosy: ezio.melotti, mbussonn, willingc priority: normal severity: normal status: open title: ast.Call signature changed type: behavior versions: Python 3.5 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24220> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
