Re: [Numpy-discussion] guide for downstream package authors & setting version constraints

Thanks for the suggestion. However I was able to solve the issue I had by just creating inline wrapper functions in cython for the C functions so I dont have to link them when importing in other 3rd party cython modules. -- Sent from: http://numpy-discussion.10968.n7.nabble.com/

Re: [Numpy-discussion] guide for downstream package authors & setting version constraints

This is a different topic altogether. I think you would get better results asking on the cython-users mailing list with a concrete example of something that didn't work. Matti On 3/6/21 7:52 PM, zoj613 wrote: Is there a best practice guide somewhere in the docs on how to correctly expose C-l

Re: [Numpy-discussion] guide for downstream package authors & setting version constraints

Thanks you, this looks very informative. Is there a best practice guide somewhere in the docs on how to correctly expose C-level code to third parties via .pxd files, similarly to how one can access the c_distributions of numpy via cython? I tried this previously and failed miserably. It seemed lik

[Numpy-discussion] guide for downstream package authors & setting version constraints

Hi all, We now have a guide for downstream package authors, talking about API and ABI stability, NumPy versioning, testing against NumPy master, and how to add build time and runtime dependencies for numpy: https://numpy.org/devdocs/user/depending_on_numpy.html Especially the version constraints