Nested requirements.txt logic is not fully complete

[Jped]

Describe the bug

We should be looking for a requirements.txt in the folder of the task, if it does not exist there we go up one parent directory until the root tasks directory.

What is currently happening is that it looks for a requirements.txt in the current directory and then if it cant find it looks for one in the root ./tasks directory.

It also makes the requirements.txt in the root directory a requirement which it doesn't necessarily have to be.

Is there an existing issue for this?

• I have searched the existing issues

Reproduction

You can create a tasks structure like this:

tasks
|__dir1
     |-requirements.txt
     |_dir2
        |_tasks.py

It will raise an error bc there is no root requirements.txt which it shouldn't, and then if you add a root req file it will use that for the tasks in tasks.py when it should be using ./tasks/dir1/requirements.txt

Screenshot

No response

Logs

None

System Info

Current

Severity

serious, but I can work around it