Message 188668 - Python tracker

➜

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	jsafrane
Recipients	amaury.forgeotdarc, benjamin.peterson, dabeaz, jsafrane, pitrou
Date	2013-05-07.15:38:15
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<51891FE4.9040104@redhat.com>
In-reply-to	<1367940530.27.0.430086592093.issue17922@psf.upfronthosting.co.za>

Content
> Right. But this is an embedded interpreter, and SWIG does not call > PyType_Ready() again; the old type is returned instead. Python crashes in Py_Initialize(). SWIG_init() is called right after it. So even if SWIG calls PyType_Ready, it would be too late. Why python remembers SWIG types after Py_Finalize() in the first place? I want to destroy it and start with fresh instance. Jan

> Right. But this is an embedded interpreter, and SWIG does not call
> PyType_Ready() again; the old type is returned instead.

Python crashes in Py_Initialize(). SWIG_init() is called right after it.
So even if SWIG calls PyType_Ready, it would be too late.

Why python remembers SWIG types after Py_Finalize() in the first place?
I want to destroy it and start with fresh instance.

Jan

History
Date	User	Action	Args
2013-05-07 15:38:15	jsafrane	set	recipients: + jsafrane, amaury.forgeotdarc, pitrou, benjamin.peterson, dabeaz
2013-05-07 15:38:15	jsafrane	link	issue17922 messages
2013-05-07 15:38:15	jsafrane	create