Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Questions about `__pyx_capi__` use/stability. #3077

Open
stuartarchibald opened this issue Aug 13, 2019 · 0 comments

Comments

@stuartarchibald
Copy link

commented Aug 13, 2019

A common use case when extending Numba is to use an existing Cython extension module to provide access points to the compiled functions contained within. For Numba to do this the __pyx_capi__ attribute must be queried. Examples and discussion here: numba/numba#3086 and API guide here http://numba.pydata.org/numba-doc/latest/extending/high-level.html#importing-cython-functions.

Recently work has started on numba-scipy to add SciPy support to Numba, this PR numba/numba-scipy#12 notes that __pyx_capi__ is a Cython internal.

The crux of all this is I think a few questions:

  1. Is __pyx_capi__ sufficiently ingrained in Cython that it can be relied upon being present indefinitely.
  2. Is __pyx_capi__ truly internal? Or are there cases in practice where users are parsing/using it (pythran does already?!)?
  3. Is the form of __pyx_capi__ stable/consistent.

Thanks in advance for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.