[Python-Dev] Call PyType_Ready on builtin types during interpreter startup? (original) (raw)
Eric Smith eric at trueblade.com
Sun Dec 28 14:54:01 CET 2008
- Previous message: [Python-Dev] Call PyType_Ready on builtin types during interpreter startup?
- Next message: [Python-Dev] Call PyType_Ready on builtin types during interpreter startup?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 PyTypeReady 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 PyObjectHash to be yet another place where PyTypeReady 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.
- Previous message: [Python-Dev] Call PyType_Ready on builtin types during interpreter startup?
- Next message: [Python-Dev] Call PyType_Ready on builtin types during interpreter startup?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]