> On 30 Jan 2020, at 18:44, John Skaller2 wrote:
>
>
>
>> On 30 Jan 2020, at 17:20, John Skaller2 wrote:
>>
>> Just FYI, trying to load my extension I get “ModuleNotFound”.
>
> ~/felix>/usr/local/opt/python/Frameworks/Python.framework/Versions/3.6/bin/python3.6m
> Python 3.6.5 (default, A
On 30. Jan 2020, at 03:52, John Skaller2 wrote:
>
> However the shared library extensions I generate will always be linked
> against a shared library. My build tech does not permit flat namespaces
> for dynamic linkage. I know you CAN get Python run time as a shared
> library on Debian based syst
> On 30 Jan 2020, at 17:20, John Skaller2 wrote:
>
> Just FYI, trying to load my extension I get “ModuleNotFound”.
using Cython I get a different result.
~/felix>cat oldtest.py
def testit():
print("Testit”)
Note the original name was test.py, changed so it cannot be loaded. Under the
orig
Just FYI, trying to load my extension I get “ModuleNotFound”.
A test *.py file in the same directory can be imported.
A check on the shared library (dylib on MacOS) shows that the required function
is exported.
Maybe my layout of the module table is wrong, its hard to say given so much
informatio
Ok, I have processed most of the Cython/Include/python/*.pxd files.
Seems these were mechanically derived from docs? Because some
of the bugs in the docs are also in these files. Not sure what you
would like to do so I’ll ask here before doing github issues.
1. Its not all there. I couldn’t find
