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 mark.dickinson
Recipients larry, loewis, mark.dickinson, pitrou
Date 2009-05-02.18:03:16
SpamBayes Score 4.923839e-14
Marked as misclassified No
Message-id <1241287399.29.0.256563732746.issue5880@psf.upfronthosting.co.za>
In-reply-to
Content
I've removed those gratuitous context uses in Objects/longobject.c
in r72202 (trunk) and r72203 (py3k).

I'm not sure it's a good idea to remove the context field completely.  
Apart from the compatibility issues that Antoine pointed out, it
doesn't seem improbable that some getters and setters might need it.

A Google code search for PyGetSetDef turned up at least one non-null
use of the context field (in something called pyephem).  I didn't
look at it closely, though.
History
Date User Action Args
2009-05-02 18:03:19mark.dickinsonsetrecipients: + mark.dickinson, loewis, pitrou, larry
2009-05-02 18:03:19mark.dickinsonsetmessageid: <1241287399.29.0.256563732746.issue5880@psf.upfronthosting.co.za>
2009-05-02 18:03:17mark.dickinsonlinkissue5880 messages
2009-05-02 18:03:17mark.dickinsoncreate