-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
Path are coerced to string #287
Comments
Some places expect it to be a string... When I added support for Since you can easily re-create a |
I see, it makes sense. It could be an issue if you have a lot of paths, then the cost of recreating all the Path objects may be noticeable (that being said, that's not an issue I have for now). If it's not worth implementing, documenting the behavior to make it less surprising can be enough I think. |
@slaperche-scality off-topic: Saw your work on metalk8s, awesome! Also glad you had only 3 (small) requests 😀 |
No problem 🙂 , I'll submit a PR for that :) (probably next week). |
The documentation mention that
doit
acceptPath
object insidefile_dep
andtargets
but I noticed that when I got the item back they're no longerPath
object but have been converted to string.e.g:
gives
I would have expected the types to be preserved.
Is it a bug or do you have some internal constraints that force you to convert everything to string?
The text was updated successfully, but these errors were encountered: