Hi, I have some question. Is it possible to have two

requirements.txt

files in separated folders for separated packages and with the same dependency (3rd part)? Because when I want to add the same dependency in second

requirements.txt

I lose the first one. I saw in docs

Dependency inference will no-op if >2 targets refer to the same file

section.

you can, but then you’ll need to explicitly specify which copy each library should use

I wonder if it makes sense to have dep inference resolve such cases by selecting the dependency that is closest to it in the filesystem ( e.g. its closest ancestor)

i think that that would be too magical. we could likely help people by erroring/warning in that case though, and requiring that they either specify a matching target explicitly. i’m not sure how to deal with false positives in that case

It's less magical if it has to be an ancestor (as opposed to some lateral relation)

Worth thinking about in the context of multiple resolves per repo, probably. because in that case you'd want the version chosen to be based on the root possibly rather than something defined on the library?