-
Notifications
You must be signed in to change notification settings - Fork 142
Encode paths with os.fsencode() #228
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
Conversation
This way, we can pass Path objects or arbitrary bytes. It also handles invalid UTF-8 paths.
|
Thanks for the submission! This makes sense to me after reading the documentation for |
|
Hi @hkpeprah. I need to figure out how to deal with the CLA for now. Sorry for the inconvenience. |
|
CLA signed 👍 |
|
You're right. It's time to drop support for Python 2. Support was dropped more than five years ago! I also noted that in the CI, Python 3.8 and 3.9 are tested. Wouldn't be more relevant if the oldest and newest supported versions were tested instead? So for instance, 3.9 and 3.13. |
|
I'll try to get this merged soon'ish. I want to #231 first because that will be a minor release, and will include this change in a major release (non-backwards compatible) where we drop Python 2. |
|
Didn't get movement on the other PR, so I will go ahead with this one and figuring out the notes for dropping Python 2. |
|
I'll be merging this now and and moving towards a major release with the cut over to Python 3. |
|
This has landed in |
This way, we can pass Path objects or arbitrary bytes. It also handles invalid UTF-8 paths.