Message 333017 - Python tracker

Message333017

Author	vstinner
Recipients	docs@python, eamanu, serhiy.storchaka, terry.reedy, vstinner
Date	2019-01-04.22:58:06
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1546642686.84.0.997362808149.issue35616@roundup.psfhosted.org>
In-reply-to

Content
I disagree. It's acceptable to break the C API in a minor release if the change has been properly promoted, documented, announced, etc. IMHO breaking the C API in 4.0 is going to send a bad signal to users. Multiple core developers asked multiple times to wait until Python 2 is really dead before removing some features which are used on Python 2 and Python 3. So at least, we must wait until January 1st, 2020, before removing Py_UNICODE APIs. I also would like to see the deprecation warning supported on Windows. I didn't see any announcement of future removal of C API on the capi-sig mailing list.

Content

I disagree. It's acceptable to break the C API in a minor release if the change has been properly promoted, documented, announced, etc.

IMHO breaking the C API in 4.0 is going to send a bad signal to users.

Multiple core developers asked multiple times to wait until Python 2 is really dead before removing some features which are used on Python 2 and Python 3. So at least, we must wait until January 1st, 2020, before removing Py_UNICODE APIs.

I also would like to see the deprecation warning supported on Windows.

I didn't see any announcement of future removal of C API on the capi-sig mailing list.

History
Date	User	Action	Args
2019-01-04 22:58:08	vstinner	set	recipients: + vstinner, terry.reedy, docs@python, serhiy.storchaka, eamanu
2019-01-04 22:58:06	vstinner	set	messageid: <1546642686.84.0.997362808149.issue35616@roundup.psfhosted.org>
2019-01-04 22:58:06	vstinner	link	issue35616 messages
2019-01-04 22:58:06	vstinner	create