RetroSearch Browse

Sun Dec 28 14:54:01 CET 2008 · https://mail.python.org/pipermail/python-dev/2008-December/084624.html

Nick Coghlan wrote:
> Nick Coghlan wrote:
>> Rather than playing whack-a-mole with this, does anyone have any ideas
>> on how to systematically find types which are defined in the core, but
>> are missing an explicit PyType_Ready call? (I guess one way would be to
>> remove all the implicit calls in a local build and see what blows up...
>> that seems a little drastic though)
> 
> The whack-a-mole tactic did pick up a couple more though - the two
> "builtin" types that iter() can return (the basic sequence iterator and
> the callable with sentinel result iterator).
> 
> 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.

Eric.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2008-December/084624.html below:

[Python-Dev] Call PyType_Ready on builtin types during interpreter startup?