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 eric.smith
Recipients amaury.forgeotdarc, eric.smith, gpolo, hagen, ncoghlan, rhettinger
Date 2008-12-28.17:33:18
SpamBayes Score 6.60317e-05
Marked as misclassified No
Message-id <1230485600.5.0.656149882555.issue4701@psf.upfronthosting.co.za>
In-reply-to
Content
> Perhaps the path of least resistance is to change PyObject_Hash to be
> yet another place where PyType_Ready will be called implicitly if it
> hasn't been called already?

I think that's the best thing to do. It would bring PyObject_Hash in
line with PyObject_Format, for example.

If we pick some other solution (instead of modifying PyObject_Hash),
then we should find all of the lazy calls to PyType_Ready (that exist to
solve this problem) and remove them. IOW, it should be handled the same
everywhere.
History
Date User Action Args
2008-12-28 17:33:20eric.smithsetrecipients: + eric.smith, rhettinger, amaury.forgeotdarc, ncoghlan, gpolo, hagen
2008-12-28 17:33:20eric.smithsetmessageid: <1230485600.5.0.656149882555.issue4701@psf.upfronthosting.co.za>
2008-12-28 17:33:18eric.smithlinkissue4701 messages
2008-12-28 17:33:18eric.smithcreate