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 amaury.forgeotdarc, benjamin.peterson, brett.cannon, christian.heimes, georg.brandl, gpolo, lemburg, mark.dickinson, pitrou, rhettinger
Date 2009-01-29.09:45:22
SpamBayes Score 2.3884337e-05
Marked as misclassified No
Message-id <1233222324.2.0.295224338617.issue1717@psf.upfronthosting.co.za>
In-reply-to
Content
If I understand Christian's plan correctly, it was to:

(1) raise TypeError for non-NULL tp_compare, and
(2) rename tp_compare to tp_reserved (with type void *).

and both of these would happen with 3.0.1, so no difference between
3.0.1 and 3.1.0.

It seems to me that if tp_compare is actually going to be removed then
that should be done in 3.0.1;  else third-party stuff that works with
3.0.x will fail with 3.1, due to the various tp_* fields being out of sync.

It would be nice not to have tp_reserved hanging around for the duration
of 3.x.  (Similarly for nb_reserved.)
History
Date User Action Args
2009-01-29 09:45:24mark.dickinsonsetrecipients: + mark.dickinson, lemburg, brett.cannon, georg.brandl, rhettinger, amaury.forgeotdarc, pitrou, christian.heimes, benjamin.peterson, gpolo
2009-01-29 09:45:24mark.dickinsonsetmessageid: <1233222324.2.0.295224338617.issue1717@psf.upfronthosting.co.za>
2009-01-29 09:45:23mark.dickinsonlinkissue1717 messages
2009-01-29 09:45:22mark.dickinsoncreate