homepage

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 Trundle, benjamin.peterson, daniel.urban, eric.araujo, ncoghlan, pitrou, rhettinger
Date 2011年04月06日.14:48:57
SpamBayes Score 3.9267716e-06
Marked as misclassified No
Message-id <1302101341.7.0.44041677689.issue10977@psf.upfronthosting.co.za>
In-reply-to
Content
Having convinced myself that Raymond's original suggestion can't be implemented safely, I have an alternative (arguably even more radical) proposal:
Deprecate the public concrete API functions that modify object state.
Put an underscore in front of them for internal use, have the public versions trigger a deprecation warning (not to be removed until 3.6 or so), provide a C level mechanism to easily make the equivalent of a super() call and advise that everyone switch to the abstract API in order to handle subclasses properly.
History
Date User Action Args
2011年04月06日 14:49:01ncoghlansetrecipients: + ncoghlan, rhettinger, pitrou, benjamin.peterson, eric.araujo, Trundle, daniel.urban
2011年04月06日 14:49:01ncoghlansetmessageid: <1302101341.7.0.44041677689.issue10977@psf.upfronthosting.co.za>
2011年04月06日 14:48:57ncoghlanlinkissue10977 messages
2011年04月06日 14:48:57ncoghlancreate

AltStyle によって変換されたページ (->オリジナル) /