Message 243427 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	mbussonn
Recipients	ezio.melotti, mbussonn, willingc
Date	2015-05-17.20:10:37
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1431893438.07.0.469229426161.issue24220@psf.upfronthosting.co.za>
In-reply-to

Content
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 ?

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 ?

History
Date	User	Action	Args
2015-05-17 20:10:38	mbussonn	set	recipients: + mbussonn, ezio.melotti, willingc
2015-05-17 20:10:38	mbussonn	set	messageid: <1431893438.07.0.469229426161.issue24220@psf.upfronthosting.co.za>
2015-05-17 20:10:37	mbussonn	link	issue24220 messages
2015-05-17 20:10:37	mbussonn	create