Skip to content

Bug: pyproject.toml lists 'pip' as runtime dependency and hard-pins numpy version #6

@Ashwinhegde19

Description

@Ashwinhegde19

Bug Description

pyproject.toml has two packaging issues in the dependencies list:

1. pip listed as a runtime dependency

"pip",

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 ==

"numpy==2.2.6",

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions