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 ncoghlan
Recipients docs@python, ncoghlan, njs
Date 2016-07-13.01:32:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1468373521.97.0.915242819681.issue27505@psf.upfronthosting.co.za>
In-reply-to
Content
Python 3.5 added the ability to set module __class__ attributes by way of http://bugs.python.org/issue22986

However, this isn't covered in the What's New guide or anywhere else in the documentation, and even in the NEWS file it appears under the cryptic title "Issue #22986: Allow changing an object’s __class__ between a dynamic type and static type in some cases." for 3.5.0a1

This should be documented somewhere (perhaps in the data model section of the language reference?) and an example given of using the feature to emit DeprecationWarning for access to a particular module level attribute.

It should also be mentioned in the Python 3.5 What's New documentation.
History
Date User Action Args
2016-07-13 01:32:02ncoghlansetrecipients: + ncoghlan, njs, docs@python
2016-07-13 01:32:01ncoghlansetmessageid: <1468373521.97.0.915242819681.issue27505@psf.upfronthosting.co.za>
2016-07-13 01:32:01ncoghlanlinkissue27505 messages
2016-07-13 01:32:01ncoghlancreate