Skip to content
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

Python Paths #163

Open
sjunges opened this issue May 13, 2024 · 1 comment
Open

Python Paths #163

sjunges opened this issue May 13, 2024 · 1 comment

Comments

@sjunges
Copy link
Contributor

sjunges commented May 13, 2024

Our functions that take paths as input currently expect strings. Should we instead allow (or even enforce) pathlib.Path?

@volkm
Copy link
Contributor

volkm commented May 14, 2024

I would be in favor of using pathlib.Path.
My approach would be twofold: we first use pathlib.Path but allow strings as a fall-back (and give a deprecation warning). Later, we can remove string support altogether. Or should we simply migrate at once?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants