On 31/01/20 9:47 am, John Skaller2 wrote:
2. pyport is plain wrong. It contains conflicting C typedefs.
PRs welcome.
Is this your prefered method (pull request)?
I'm sure PRs are very welcome, but at the least you could
give us some idea of what these conflicting typedefs are!
ob
On 31/01/20 10:00 am, John Skaller2 wrote:
It works. Why Python would look for a linux extension only on MacOS I have no
idea.
It's not really a Linux extension. It goes back to when shared
libraries first appeared in BSD, from which large parts of MacOSX
are derived, and MacOSX also recognise
> On 30 Jan 2020, at 22:23, Greg Ewing wrote:
>
> On 30/01/20 8:58 pm, John Skaller2 wrote:
> import oldtest
> > Traceback (most recent call last):
> >File "", line 1, in
> > ModuleNotFoundError: No module named 'oldtest'
> What happens if you use a .so extension instead of .dylib?
I
> On 31 Jan 2020, at 00:22, Stefan Behnel wrote:
>
>> Seems these were mechanically derived from docs?
>
> They were manually copied over time.
Ouch. A lot of work.
>> 2. pyport is plain wrong. It contains conflicting C typedefs.
>
> PRs welcome.
Is this your prefered method (pull request)
John Skaller2 schrieb am 30.01.20 um 03:47:
> Ok, I have processed most of the Cython/Include/python/*.pxd files.
>
> Seems these were mechanically derived from docs?
They were manually copied over time.
> Because some of the bugs in the docs are also in these files. Not sure what
> you
> woul
On 30/01/20 8:58 pm, John Skaller2 wrote:
import oldtest
> Traceback (most recent call last):
>File "", line 1, in
> ModuleNotFoundError: No module named 'oldtest'
What happens if you use a .so extension instead of .dylib?
--
Greg
___
cython-
OMG. I don’t believe it.
Renaming the binary from *.dylib to *.so fixed it.
Both the Cython and Felix shared libraries can be imported and both run.
Sorry for the noise. Just didn’t occur to me that Python would want *.so
filenames on MacOS.
Until I remembered seeing some in Cython build direct
> On 30 Jan 2020, at 18:00, Yury V. Zaytsev wrote:
>
> 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
