@jaraco courtesy ping to put this on your radar

This changes behaviour of str(zipp.Path(...)), so we'd need to add a .. versionchanged:: directive in the cpython docs.

I think the change is worthwhile, because the current behaviour:

• Produces strings that can be mistaken for a real filesystem paths by a casual reader
• Produces strings that mix forward and backward slashes on Windows
• Raises a TypeError when the zip file doesn't have a name on the filesystem
• Doesn't have a clear use case (as far as I can tell)
• Is slightly less intuitive than returning the member path alone imo

IIUC, the current implementation is designed to be "lossless" - all the arguments to __init__() are represented in the __str__() return value. But is losslessness a requirement or even an expectation of __str__(), __int__(), etc? IMHO it's fine to omit contextual information (in this case, the ZipFile object) if the main value is represented. Furthermore the current implementation isn't truly lossless because Path("a", at="b.zip") and Path("a/b.zip") can't be distinguished from their string representations.

What do you think? Thanks

After some consideration in #134, I'd feel better about having a :zipfile: in the output, so I've implemented that approach instead. Let's go forward with this (for now), but I'm happy to revisit/iterate further.

Released as 3.23.1