find's max_depth off by one?

Question

find's max_depth off by one?

Closed this issue 8 years ago · 4 comments

find with max_depth=1 will fail even if pipfile is in the current directory. Is that intentional?

Answer 1 · 2017-02-01T21:27:11.000Z

this code is being rewritten

Answer 2 · 2017-02-01T21:29:45.000Z

Ok. I understand that. Will the api stay the same? Will there be a find after the rewrite is complete? If yes, will it have a max_depth parameter? If yes, what will be the semantics of that max_depth?

Answer 3 · 2017-02-01T23:29:49.000Z

who knows? that's entirely dependent upon #57

Answer 4 · 2017-02-02T14:21:12.000Z

Hmmm, that seems interesting. I do think this should be fixed for those who use the current version, but I'll close this for now.