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 vstinner
Recipients Anthony Sottile, ethan smith, gregory.p.smith, gvanrossum, levkivskyi, lukasz.langa, miss-islington, vstinner
Date 2019-06-11.23:14:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560294866.44.0.272981037502.issue35766@roundup.psfhosted.org>
In-reply-to
Content
> But this is the format currently used by typed_ast. I think it would just cause a cascade of annoying failures for tools that switch between typed_ast and the 3.8 version of ast. Such as mypy.

typed_ast is a 3rd party project. But here we are talking about Python stdlib. If a project moves from typed_ast to stdlib ast, IMHO it should be quite easy to replace 4 with (3, 4), especially if 4 raises an error, no?

IMHO it's a good opportunity to fix it.

I would prefer to not have to batch many backward incompatible changes into Python 4...
History
Date User Action Args
2019-06-11 23:14:26vstinnersetrecipients: + vstinner, gvanrossum, gregory.p.smith, lukasz.langa, levkivskyi, Anthony Sottile, ethan smith, miss-islington
2019-06-11 23:14:26vstinnersetmessageid: <1560294866.44.0.272981037502.issue35766@roundup.psfhosted.org>
2019-06-11 23:14:26vstinnerlinkissue35766 messages
2019-06-11 23:14:26vstinnercreate