Best practices for distributing and testing an interface file
Matti Picus <[email protected]> Tue, 2 Mar 2021 15:56:29 +0200
| Newsgroups | gmane.comp.programming.swig |
|---|---|
| Message-ID | <[email protected]> |
Over at NumPy, we have a numpy.i SWIG interface file, but are not distributing it with our python wheels or source tarball. Two reasons: we do not really know where to put it, and we do not have good tests for it. How are people testing their interface files? Are there coverage-like tools to determine which parts of the file have been tested? Are there some liberally licensed examples we could add to our CI? We occasionally get requests to modify the file, and are hesitant to do so until we know we will not break anything. Are there any domain experts who would like to be the NumPy SWIG expert? For instance, this PR seems harmless, but who knows without tests https://github.com/numpy/numpy/pull/18522 Thanks, Matti _______________________________________________ Swig-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/swig-user