Message 338789 - Python tracker

➜

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	serhiy.storchaka
Recipients	josh.r, matrixise, ronaldoussoren, serhiy.storchaka, steve.dower
Date	2019-03-25.08:19:21
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
I am against deprecating READONLY. This will break virtually every third-party extension that use it. Many projects are strong about compiler warning and will need to rewrite the code that worked for years. I think that we can add the deprecation warning only after the last version that do not have PY_READONLY (3.7) will be no longer supported. I.e. in 3.11 or something around. Also I am not sure about using enums for flags. Would not this cause problems on C++? Since this is an extending of the C API, it would be better to discuss the necessary of adding PY_READWRITE on Python-Dev.

I am against deprecating READONLY. This will break virtually every third-party extension that use it. Many projects are strong about compiler warning and will need to rewrite the code that worked for years.

I think that we can add the deprecation warning only after the last version that do not have PY_READONLY (3.7) will be no longer supported. I.e. in 3.11 or something around.

Also I am not sure about using enums for flags. Would not this cause problems on C++?

Since this is an extending of the C API, it would be better to discuss the necessary of adding PY_READWRITE on Python-Dev.

History
Date	User	Action	Args
2019-03-25 08:19:21	serhiy.storchaka	set	recipients: + serhiy.storchaka, ronaldoussoren, steve.dower, matrixise, josh.r
2019-03-25 08:19:21	serhiy.storchaka	set	messageid: <[email protected]>
2019-03-25 08:19:21	serhiy.storchaka	link	issue36347 messages
2019-03-25 08:19:21	serhiy.storchaka	create