Author gvanrossum
Recipients christian.heimes, collinwinter, gvanrossum
Date 2007-11-30.22:51:12
SpamBayes Score 0.00439318
Marked as misclassified No
Message-id <ca471dc20711301451p410b5bfdx670364d87a57d6f0@mail.gmail.com>
In-reply-to <1196462699.92.0.118593005345.issue1504@psf.upfronthosting.co.za>
Content
> Whatever you say. But shouldn't we make people to use types.MethodType()
> or whatever we use as the new module for PyMethod_Type()? People are
> going to use types.MethodType() when they see the deprecation warning.

Well, if new.method is deprecated, then types.MethodType should be
doubly deprecated. The types module was only ever intended for type
checking, not for creating new instances.

The correct solution will be to use whatever we end up deciding about
pyvm. Certainly the types module will go.

Maybe new in 2.6 should be a -3 deprecation only?
History
Date User Action Args
2007-11-30 22:51:12gvanrossumsetspambayes_score: 0.00439318 -> 0.00439318
recipients: + gvanrossum, collinwinter, christian.heimes
2007-11-30 22:51:12gvanrossumlinkissue1504 messages
2007-11-30 22:51:12gvanrossumcreate