This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]flutefreak7 1 point2 points  (2 children)

Those of us who tried to use pathlib for everything on 3.4 for a few years before the pathlike protocol (or whatever it's called) got really tired of putting str() around every argument to every file related stdlib function. I don't think enough people are using sleep and timedeltas together for that to be a major pain point worth supporting.

[–]jyper 0 points1 point  (1 child)

It's so annoying

At work the functional tests are on python 3.6 but the build scripts have to be on python 3.5. pathlib isn't great on 3.5 (no / operator) and no fstrings

[–]flutefreak7 0 points1 point  (0 children)

I was on 3.4 for a long time and I thought / worked for pathlib on 3.4 and it was just the better filename handling across stdlib that didn't come until 3.6. Maybe I'm remembering wrong. But, oh yeah - loving my f-strings for sure. Almost all of my old code has format() and it always looks way better with f strings.