On Tue, Jul 16, 2019 at 11:07 PM Jeroen Demeyer <j.deme...@ugent.be> wrote: > > On 2019-07-16 15:33, Inada Naoki wrote: > >> We currently have a deprecation policy saying that functions deprecated > >> in version N cannot be removed before version N+2. That's a reasonable > >> policy but some deprecation purists insist that it MUST (instead of MAY) > >> be removed in version N+2. Following this reasoning, we cannot deprecate > >> something that we cannot remove. > > > > Really? Any example? > > * https://bugs.python.org/issue29548#msg287775 >
OK, Stable ABI was special. We can not remove it until Python 4 regarding to PEP 384. In 2017, Python 4 was looked like "forever". But for now, we should think Python 4 is the real future in 2020s, not 3000 or 4000. I think we should deprecate APIs in stable API like non-stable API if we want to remove it after Python 4.0. -- Inada Naoki <songofaca...@gmail.com> _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/WR4SE2GFZHW2CFD6C7Z4BI7A2FWK5SMQ/
