I'm beta testing a tool for automatically converting os.path to pathlib.Path calls. This repository uses both, making it a good candidate to choose one consistently.
Coverage remained the same at 100.0% when pulling e8af6ad7d8aa1c128f935c6b0fe04fd137557387 on sbrugman:master into 4cd79bc8af55fb0f34a2a39b2e38f0e71c208fd4 on kmkurn:master.
I'm beta testing a tool for automatically converting
os.path
topathlib.Path
calls. This repository uses both, making it a good candidate to choose one consistently.For background, one could read these blog posts by Trey Hunner: Why you should be using Pathlib and No really, pathlib is great.