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 grahamd
Recipients daniel.urban, grahamd, rhettinger
Date 2013-09-30.07:17:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1380525477.42.0.283898423251.issue19072@psf.upfronthosting.co.za>
In-reply-to
Content
If you have the time, would be great if you can have a quick look at my wrapt package. That will give you an idea of where I am coming from in suggesting this change.

http://wrapt.readthedocs.org/en/latest/
http://wrapt.readthedocs.org/en/latest/issues.html
http://wrapt.readthedocs.org/en/latest/decorators.html
http://wrapt.readthedocs.org/en/latest/examples.html

In short, aiming to be able to write decorators which are properly transparent and aware of the context they are used in, so we don't have this silly situation at the moment where it is necessary to write distinct decorators for regular functions and instance methods. A classmethod around another decorator was the one place things will not work as would like to see them work.

I even did a talk about writing better decorators at PyCon NZ. Slides with notes at:

http://lanyrd.com/2013/kiwipycon/scpkbk/

Thanks.
History
Date User Action Args
2013-09-30 07:17:57grahamdsetrecipients: + grahamd, rhettinger, daniel.urban
2013-09-30 07:17:57grahamdsetmessageid: <1380525477.42.0.283898423251.issue19072@psf.upfronthosting.co.za>
2013-09-30 07:17:57grahamdlinkissue19072 messages
2013-09-30 07:17:57grahamdcreate