Closed mgeier closed 1 month ago
seems all a bit hacky.
I think the idea of the deprecation is that Sphinx eventually wants to return pathlib paths from these APIs.
So maybe a better fix would be to wrap the instances of these that represent concrete filesystem paths in pathlib.Path
and using its APIs instead of string manipulation. But I didn’t take a deeper look here.
It sure is hacky, but contrary to the Sphinx maintainers, I value backwards compatibility, and I am somewhat confident that my PR here will continue to work with old versions (as well as new versions), while if I switch everything to pathlib
, it will break when using old Sphinx versions, right?
no I mean wrapping the return values of that API in Path(...)
then you don’t need to use string operations on paths anymore
Hey @mgeier,
Is this PR getting merged soon? I have a failing pipeline and do not want to filterwarnings
the error.
@callezenwaka
Is this PR getting merged soon? I have a failing pipeline and do not want to
filterwarnings
the error.
Yes, I'm planning to merge this soon, I just wanted to respond to @flying-sheep's comments first.
It would be great if you could test this on your project(s) and report if it works or not!
I'm going to merge this now, because people seem to be waiting for a fix, but I'm still open for changes which I can incorporate at a later time.
Thanks for responding! Sorry for holding this up with my curiosity!
No worries, I like getting feedback!
Hopefully fixes #804.