Date: Fri, 5 Jan 2024 21:03:01 +1300 From: Matthew Luckie <mjl@luckie.org.nz> To: freebsd-python@freebsd.org Subject: cython code release best practices supporting packaging Message-ID: <ZZe3taqolJ9Xtf7g@pi4.luckie.org.nz>
next in thread | raw e-mail | index | archive | help
Hi, I have written a python interface to a C library that I maintain, using cython, and am looking for advice on how to structure the code release so that packaging is as straightforward as possible. My inclination is to include the python interface with the source code of the C library, as the python interface is tightly coupled with the library. I've done some preliminary investigation, and have found libimobiledevice in ports -- devel/py-libplist, comms/py-libimobiledevice, etc. I am wondering if there is other software in ports heavily tied to a C library with cython that freebsd python maintainers recommend as supporting best practices for packaging, that I should carefully study. The C library uses autotools (autoconf, automake, libtool). Thanks, Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZZe3taqolJ9Xtf7g>