-
Notifications
You must be signed in to change notification settings - Fork 251
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
Prefer pathlib #555
Prefer pathlib #555
Conversation
d9cf8c3
to
401a0de
Compare
Hi, Steps I've done:
Result:
I'm on Windows 11 OS, powershell environment. Please consider merging this branch ASAP for next poetry release, thank you. |
I think we can include this in a patch release (and bump the required core version in the next poetry patch release). However, I don't want to remove any deprecation in a patch release (even if it is unlikely anybody still uses it). Do you mind if I drop the first commit in this PR? (You're welcome to create a deprecation removal PR for the next minor release if you like. There might be some more things that are deprecated for a long time.) |
feel free to rearrange as you wish (per opening remarks, I'd intended this series as more of a tidying-up sequence of commits rather than actually-fixes-something; it's mostly luck that it turns out to fix something that someone cares about) |
5fe4864
to
b1d3604
Compare
b1d3604
to
accd3fc
Compare
Kudos, SonarCloud Quality Gate passed! |
I've been sitting for a while on some tweaks to move poetry-core in the direction of preferring
pathlib
overos
for file and path manipulations, but they've not seemed interesting enough to be worth an MR.However I notice that they in passing should fix python-poetry/poetry#7505, which makes it all seem a bit more worthwhile.
This first push deliberately doesn't include the fixes - I'm using the CI pipeline to do my windows testing and am hoping to see that the testcase that I've added fails, per that issue. Then I'll follow up with the changes that are supposed to fix it.