A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] Call PyType_Ready on builtin types during interpreter startup? [Python-Dev] Call PyType_Ready on builtin types during interpreter startup?Nick Coghlan ncoghlan at gmail.com
Sat Dec 20 08:17:28 CET 2008
Nick Coghlan wrote:
> Is there a specific reason for not fully initialising the builtin types?
> Or should we be calling PyType_Ready on each of them from _PyBuiltin_Init?

I need to correct this slightly: some builtin types *are* initialised
properly by _Py_ReadyTypes.

So the question is actually whether or not the missing builtin types
should be added to that function.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
---------------------------------------------------------------
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4