Skip to content

Make it easier to load wheels from the local file system #1689

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

Open
georgevreilly-stripe opened this issue Jan 12, 2024 · 1 comment
Open

Comments

@georgevreilly-stripe
Copy link

🚀 feature request

Relevant Rules

Possibly in whl_library, but more likely in requirements.txt

Description

I had created a patched wheel that I wished to test with Bazel and rules_python before publishing it to our internal Artifactory package index. There was no easy way to accomplish this.

I eventually worked out that I could test my patched wheel by using pip2pi to create a local package index on my filesystem, then adding --index-url=/tmp/pypi/simple to the beginning of my requirements.txt.

See this writeup for full details.

Describe the solution you'd like

If you have a solution in mind, please describe it.

I think the easiest thing for users is if they can specify a file path in requirements.txt; e.g.,

sympy==1.12
./tmp/torch-2.1.0+stripe.5-cp38-cp38-manylinux1_x86_64.whl
triton==2.1.0

Pip allows this, after all.

Describe alternatives you've considered

Have you considered any alternative solutions or workarounds?
Copy link

This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days.
Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_python!

@github-actions github-actions bot added the Can Close? Will close in 30 days if there is no new activity label Jul 12, 2024
@aignas aignas removed the Can Close? Will close in 30 days if there is no new activity label Jul 23, 2024
@aignas aignas added this to the v1.0.0 milestone Jul 23, 2024
@aignas aignas removed this from the v1.0.0 milestone Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants