Bug Description
pyproject.toml has two packaging issues in the dependencies list:
1. pip listed as a runtime dependency
pip is a package manager, not a library. Listing it as a runtime dependency has no effect and is incorrect. It should be removed.
2. numpy hard-pinned with ==
Hard-pinning with == in a library's pyproject.toml forces all users and downstream environments to use exactly that patch version. This causes installation conflicts for anyone who has a different NumPy version installed.
Fix
# Remove pip entirely
# Change numpy pin to a range:
"numpy>=2.0,<3",
Impact
Anyone trying to install tribev2 alongside other packages that require a different NumPy version will hit a dependency conflict immediately.
Bug Description
pyproject.tomlhas two packaging issues in thedependencieslist:1.
piplisted as a runtime dependency"pip",pipis a package manager, not a library. Listing it as a runtime dependency has no effect and is incorrect. It should be removed.2.
numpyhard-pinned with=="numpy==2.2.6",Hard-pinning with
==in a library'spyproject.tomlforces all users and downstream environments to use exactly that patch version. This causes installation conflicts for anyone who has a different NumPy version installed.Fix
Impact
Anyone trying to install
tribev2alongside other packages that require a different NumPy version will hit a dependency conflict immediately.