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

Componentized requirement files don't work #43

Open
ingoweiss opened this issue Sep 8, 2023 · 4 comments
Open

Componentized requirement files don't work #43

ingoweiss opened this issue Sep 8, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@ingoweiss
Copy link

ingoweiss commented Sep 8, 2023

I "componentize" my requirement files into common and dev requirements such that my requirements.txt looks like this:

-r requirements/common.txt

hatch-requirement-txt does not appear to support this syntax. Build doesn't fail but my library ends up having no dependencies

@ingoweiss ingoweiss added the bug Something isn't working label Sep 8, 2023
@hyunlee1o
Copy link

Same, i got this problem. I have to ditch this installing method if it doesn't work.

@hyunlee1o
Copy link

My requirements file is like:

--index-url https://${USER}:${PWD}@${PACKAGE_URL}
./requirements.txt

which seems pretty incompatible with this build method

@FeryET
Copy link

FeryET commented Mar 3, 2024

To add to this, this requirements.txt also does not work:

-f https://download.pytorch.org/whl/torch_stable.html

torch==2.2.1+cpu

@dschneiderch
Copy link

dschneiderch commented Sep 25, 2024

+1
given the lack of support specifying constraints in hatch (from what i can tell), i'd love to be able to use -c constraints.txt in my requirements.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants