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 lemburg, mark.dickinson, methane, serhiy.storchaka, vstinner
Date 2017-02-14.13:39:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwZWCi7WfTJS-Z3+WcZz3pMBD=xEs7gE65nGZfC6EDuGpw@mail.gmail.com>
In-reply-to <1487072258.2.0.603655547954.issue29548@psf.upfronthosting.co.za>
Content
> So they are part of stable ABI.  We can't remove them until Python 4.

Please just stop right now using "Python 4" as the starting point to
break -again- the Python world.

If you plan to remove the function, plan it right now with versions
like "in 2 cycles".

If the function is part of the stable ABI, we simply cannot remove it.
Since these functions are used outside CPython and they are part of
the stable ABI, I'm not sure anymore that there is any value to remove
them.

Maybe just document them and write "please don't use them", but don't
deprecate the functions.
History
Date User Action Args
2017-02-14 13:39:12vstinnersetrecipients: + vstinner, lemburg, mark.dickinson, methane, serhiy.storchaka
2017-02-14 13:39:12vstinnerlinkissue29548 messages
2017-02-14 13:39:12vstinnercreate