STINNER Victor <vstin...@redhat.com> added the comment:
> It's fine to document the current state. I don't think you should spend any > time *changing* the API to "future-proof" it. Ok. > I am hoping that larger changes to the compiler implementation will happen > before Python 4, which will make the whole API moot (including the "parser" > module, which should be deprecated ASAP). The compiler is excluded from the > ABI for a reason. Aha, that sounds exciting :-) I created bpo-37268 to propose to deprecate the parser module in Python 3.8. -- PyCompilerFlags changes are now documented. I made the small code changes that I wanted to do in 3.8 and master. I close the issue. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37253> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
