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 twouters
Recipients Trundle, alex, daniel.urban, eric.araujo, gvanrossum, twouters
Date 2011-03-17.17:30:43
SpamBayes Score 2.4834401e-08
Marked as misclassified No
Message-id <1300383045.52.0.853837212583.issue11470@psf.upfronthosting.co.za>
In-reply-to
Content
New version of the patch; instead of triggering at attribute *access*, this just checks when creating types and in type_setattro. It also makes the warning a newly added CompatibilityWarning. Also, instead of warning for all non-descriptors, it now only warns for PyCFunctionObjects that do not have a __self__ set, or of which __self__ is a module. (The reason for the latter being the new-ish behaviour of functions defined in modules in C getting passed something as __self__, defaulting to the module.) I've removed a few staticmethod calls from cases that do not trigger the new warning.

This patch still lacks tests and doc updates, but I'm uploading right now because the sprints apparently lose internet soonish.
History
Date User Action Args
2011-03-17 17:30:45twouterssetrecipients: + twouters, gvanrossum, eric.araujo, alex, Trundle, daniel.urban
2011-03-17 17:30:45twouterssetmessageid: <1300383045.52.0.853837212583.issue11470@psf.upfronthosting.co.za>
2011-03-17 17:30:43twouterslinkissue11470 messages
2011-03-17 17:30:43twouterscreate