Content-Length: 236193 | pFad | http://github.com/numpy/numpy/issues/28873

62 DOC: should `numpy.i` be included as part of SWIG? · Issue #28873 · numpy/numpy · GitHub
Skip to content

DOC: should numpy.i be included as part of SWIG? #28873

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

Closed
DimitriPapadopoulos opened this issue May 1, 2025 · 1 comment · Fixed by #28874
Closed

DOC: should numpy.i be included as part of SWIG? #28873

DimitriPapadopoulos opened this issue May 1, 2025 · 1 comment · Fixed by #28874

Comments

@DimitriPapadopoulos
Copy link
Contributor

Issue with current documentation:

Is this still on the agenda?

and C++ code that uses C arrays and the python module NumPy. It is
ultimately hoped that numpy.i will be included as part of the SWIG
distribution.

From swig/swig#361:

SWIG provides library code for C and C++ standard library components. I don't ever envisage it providing wrappers for 3rd party libraries like numpy as it is up to those 3rd party libraries to maintain the SWIG wrappers and @ojwb gives some good reasons why.

Idea or request for content:

Either ask SWIG to accept numpy.i for inclusion, or remove that sentence.

@DimitriPapadopoulos DimitriPapadopoulos changed the title DOC: should numpy.i be included as part of the SWIG? DOC: should numpy.i be included as part of SWIG? May 1, 2025
@ojwb
Copy link

ojwb commented May 1, 2025

@DimitriPapadopoulos Please be mindful that if you quote text containing an @ mention then the person mentioned gets a notification from github and subscribed to the ticket - in this case I woke up to three useless extra notifications and two extra useless subscriptions.

The upstream ticket linked to gives SWIG point of view on this, and clearly no further input from me is needed since it's resolved already. Having to visit tickets to see why I was mentioned and then unsubscribe myself because it's not relevant just eats into the limited time I have to work on SWIG.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/numpy/numpy/issues/28873

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy