4f0eba1efd
EXT_SUFFIX, according to PEP 3149, refers to the full tag and extension for compiled extension module objects, eg .cpython-311.so, .cpython-313t.so, etc. We do not use the correct semantic meaning, and this usage becomes ambiguous and confusing when tags do not match between bytecode and compiled extension module objects. Rename our PYTHON_EXT_SUFFIX to PYTHON_TAG to align with PEP 3147's specification of a magic tag, which consists of implementation name and shorthand version only. This is meant for bytecode and other files containing this tag in their filename that do not depend on a specific Python ABI for the same version. Chase all existing consumers. Introduce PYTHON_SOABI to align with PEP 3149's specification of a tag, which consists of implementation name, shorthand version and any ABI flags present (this and PYTHON_TAG are identical without ABI flags). This is meant for compiled extension module objects and other files that depend on a specific Python ABI for the same version. Add documentation for these variables that our PYTHON_EXT_SUFFIX never had. PR: 274671 Event: Kitchener-Waterloo Hackathon 202506
39 lines
988 B
Makefile
39 lines
988 B
Makefile
PORTNAME= annoy
|
|
DISTVERSIONPREFIX= v
|
|
DISTVERSION= 1.17.3
|
|
PORTREVISION= 1
|
|
CATEGORIES= math
|
|
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
|
|
|
|
MAINTAINER= yuri@FreeBSD.org
|
|
COMMENT= Approximate Nearest Neighbors algorithm
|
|
WWW= https://github.com/spotify/annoy
|
|
|
|
LICENSE= APACHE20
|
|
LICENSE_FILE= ${WRKSRC}/LICENSE
|
|
|
|
TEST_DEPENDS= ${PYTHON_PKGNAMEPREFIX}h5py>0:science/py-h5py@${PY_FLAVOR} \
|
|
${PYNUMPY}
|
|
|
|
USES= python
|
|
USE_PYTHON= distutils autoplist pytest # tests fail because nose is broken
|
|
|
|
USE_GITHUB= yes
|
|
GH_ACCOUNT= spotify
|
|
|
|
TEST_ENV= ${MAKE_ENV} PYTHONPATH=${STAGEDIR}${PYTHONPREFIX_SITELIBDIR}
|
|
TEST_WRKSRC= ${WRKSRC}/test
|
|
|
|
post-install:
|
|
@${STRIP_CMD} ${STAGEDIR}${PYTHON_SITELIBDIR}/annoy/annoylib${PYTHON_TAG}.so
|
|
|
|
do-test:
|
|
cd ${TEST_WRKSRC} && \
|
|
${ECHO} "saving data" && \
|
|
${SETENV} ${TEST_ENV} ${PYTHON_CMD} ${FILESDIR}/test-save.py && \
|
|
${ECHO} "loading data" && \
|
|
${SETENV} ${TEST_ENV} ${PYTHON_CMD} ${FILESDIR}/test-load.py && \
|
|
${ECHO} "tests succeeded"
|
|
|
|
.include <bsd.port.mk>
|