-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revistting tmt
's Path
usage
#3283
Comments
It is. But that was added in Python 3.12. To me, it's a matter of convenience. E.g. https://github.com/teemtee/tmt/pull/3263/files#diff-80e5ba103da9529bd832a9cb0ea2712ceeee94b3dd5f92fcc75ed492817366b7R48. I really don't understand the reasoning behind not adding support for "append" to I guess the question is, where does it stand in your way, and why would you like to get rid of it? Maybe we can find some solution. |
Primarily the issue is when iteracting with other modules that generate a |
Fair enough. It's really a shame there is no If we decide to drop the class, we would need to replace its methods, probably with some |
Yeah, the OOP interface is much neater, and backports for stdlib can be quite tricky, since you cannot rely on In principle the current approach could still work, but we need to be confident that |
Could we track why we need a custom
Path
object? Reading the docstring, isn'tpathlib.Path.relative_to(walk_up=True)
what is needed there?The text was updated successfully, but these errors were encountered: