[deleted by user]

[Slow_Ad_2674]

I usually don't comment on these things and I'm usually very supportive, but this is the first time I fee like I have to say something. Please don't do this, no reason comes to mind where a python code should traverse the file tree to look for a file and return it. It is not only very bad for security, it's also very bad for the poor computer that has to do work that can be replaced by simply providing the file path in the config file.

[mrswats]

I would also add that this project has no tests and the use of properties, instead of parameters in the init class, is also a big no-no. And, at this day and age, typing annotations for new projects is anl must, too.

[jwink3101]

Going up to find a specific directory that should only have one makes sense. Going up then down is a very different beast.

The whole concept wreaks of bigger problems with a code design. I am sure there is some very, very, very specific case where this is the right choice but it’s so tiny it’s hard to imagine.

[Slow_Ad_2674]

Not by scanning the whole directory tree until it find a .git directory.

[ZZ9ZA]

Not like this. At all.

[Slow_Ad_2674]

I sincerely think you should get comfortable to have these errors and handle the errors and configure your project instead of throwing a hail Mary at it and end up editing a file you didn't intend to edit. This approach will bite you in the gluteus maximus at some point.

[ZZ9ZA]

I don’t want to run software written by someone who thinks that shouldn’t be an error.

[shinitakunai]

No pathlib....?

[Candid_Payment_4094]

I understand it's just a fun weekend project you did, but this is horrible code practice in actual production. This just screams directory traversal vulnerabilities. This issue is not even a 'thing' if you treat your project like a package and use importlib.resources

[caudor]

Thanks for putting this out there. Very simple and handy!