➜

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 Alexander.Belopolsky, Christophe Simonis, alonho, anacrolix, belopolsky, eckhardt, ironfroggy, jackdied, jcea, ncoghlan, r.david.murray, rhettinger, ssadler
Date 2013-10-26.01:57:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7eV-ZChq4k6PM=5His3GCR79P-ynR67M=_Z63yEfOmR4w@mail.gmail.com>
In-reply-to <1382729275.27.0.204835137059.issue4331@psf.upfronthosting.co.za>
Content 
On 26 Oct 2013 05:28, "alon horev" <report@bugs.python.org> wrote:
> Is the first option what you had in mind?

That's actually an interesting question. I was going to say yes, but then I
realised it would be better to just "do the right thing" when the
underlying object was a classmethod descriptor, rather than composing them
the other way around.

That view means we should be delegating __get__ to the underlying
descriptor and responding appropriately to the result. And for __call__ we
then can't play games at all, since what my sketch does would be wrong when
wrapping staticmethod.

We also need to make sure the descriptor does the right thing when
@abstractmethod is involved.
History
Date User Action Args
2013-10-26 01:57:43ncoghlansetrecipients: + ncoghlan, rhettinger, jcea, belopolsky, ironfroggy, jackdied, Christophe Simonis, ssadler, eckhardt, r.david.murray, Alexander.Belopolsky, anacrolix, alonho
2013-10-26 01:57:43ncoghlanlinkissue4331 messages
2013-10-26 01:57:42ncoghlancreate