Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Being less restrictive on numpy and pandas dependencies #7701

Open
tarun292 opened this issue Jan 16, 2025 · 0 comments
Open

Being less restrictive on numpy and pandas dependencies #7701

tarun292 opened this issue Jan 16, 2025 · 0 comments
Labels
user experience reducing friction for users

Comments

@tarun292
Copy link
Contributor

🚀 The feature, motivation and pitch

Currently in our pyproject.toml we're hardcoding to a certain version of numpy and pandas. These libraries are very commonly used in other model repos and there's a high probability that this will already be installed on a user's machine when they try to install ExecuTorch.

Can we make our numpy dependency less restrictive and instead limit numpy compatibility to a range of versions e.g. numpy>=2.1, numpy<3? Same with the pandas dependency. This will ensure that we don't cause dependency conflicts when users install ExecuTorch.

Alternatives

No response

Additional context

No response

RFC (Optional)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
user experience reducing friction for users
Projects
Status: To triage
Development

No branches or pull requests

1 participant