Author scoder
Recipients brett.cannon, loewis, pitrou, scoder
Date 2012-11-04.08:30:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1352017846.57.0.381681266787.issue16392@psf.upfronthosting.co.za>
In-reply-to
Content
The problem is a) that the module does not necessarily know to which place it eventually gets installed (Cython relies on the distutils Extension not lying to it, for example, which people do from time to time), and b) that the call to Py_InitModule() only receives the plain module name, not the package path. And yes, as mentioned in the other issue, passing a pointer to a context description struct into the module init function would have been the right thing to change for Py3 and still is the right thing to change for Py4.

BTW, I can confirm that registering the module in sys.modules explicitly right after creation works around this issue. Given that Cython needs to know the FQMN at compile time anyway, this works for us. It still leaves the problem open for other extension code.
History
Date User Action Args
2012-11-04 08:30:46scodersetrecipients: + scoder, loewis, brett.cannon, pitrou
2012-11-04 08:30:46scodersetmessageid: <1352017846.57.0.381681266787.issue16392@psf.upfronthosting.co.za>
2012-11-04 08:30:46scoderlinkissue16392 messages
2012-11-04 08:30:46scodercreate