➜

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 steve.dower
Recipients Mark.Shannon, ammar2, christian.heimes, lunixbochs2, steve.dower, vstinner
Date 2021-01-23.00:33:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <ef94cb11-3cba-658f-8188-8ea87f415308@python.org>
In-reply-to <1611360061.44.0.985597923993.issue42800@roundup.psfhosted.org>
Content 
> I think it could make sense to:
> 1. Alias READ_RESTRICTED to a new READ_AUDIT flag and use the latter instead, as it is more clear.
> 2. Update the newtype docs to mention READ_AUDIT and remove documentation for the the unused RESTRICTED flags.
> 3. Deprecate the non-functional RESTRICTED flags if that's possible?
> 4. Only cross the setattr/delattr audit flag bridge if a future refactor calls for it.

Sounds good to me. We can deprecate RESTRICTED with no intention to 
remove it, since it's documented.

Do you want to prepare a PR for this?
History
Date User Action Args
2021-01-23 00:33:41steve.dowersetrecipients: + steve.dower, vstinner, christian.heimes, Mark.Shannon, ammar2, lunixbochs2
2021-01-23 00:33:41steve.dowerlinkissue42800 messages
2021-01-23 00:33:41steve.dowercreate