The glossary should also explain a bytestring and say a bytestring and bytes-like-object are the same in Python.

[hyperkai]

According to the explanation of typing.ByteString, it seems like a bytestring is the same as a bytes-like-object in Python.

So, the glossary should also explain a bytestring and say a bytestring and bytes-like-object are the same in Python.

[cmaloney]

There's an issue here that "bytes-like" in the docs doesn't always mean "supports buffer protocol"; the particular order of checks + what types are supported varies across instances. There's both __bytes__ an the buffer protocol. One example where this came up: #138703

[JelleZijlstra]

typing.ByteString is deprecated and soon to be removed, it shouldn't be used to motivate putting something in the glossary.

[hyperkai]

Both typing.ByteString and collections.abc.ByteString will be removed in version 3.17, right? according to this memo below:

Deprecated since version 3.12, will be removed in version 3.17: The ByteString ABC has been deprecated.

[abrlake]

On Windows, Python treats backslashes as escape characters (\t, \n, etc.),
so copying a path directly from Explorer can cause weird results like tabs showing up.

You can either use a raw string like r"D:\testfolder" or normalize the path automatically.

If you want a one-liner that also cleans ../ and expands ~ for cross-platform use,
you can try this tiny utility I wrote called ipathy:

from ipathy import ipathy
print(ipathy("D:\\testfolder"))
# → D:/testfolder

[ZeroIntensity]

@abrlake That doesn't seem related to this issue. Please don't advertise your project on here.

[Yashp002]

I'd like to work on this. I'll add a 'bytestring' entry to the glossary clarifying its relationship to bytes-like objects, referencing the typing.ByteString documentation.

[cmaloney]

@Yashp002 hyperkai already made a patch; The current plan, which the "pending" label indicates, is to close this and not change the glossary entry as it's going away in Python 3.17. Definitely lots of other good issues to work on :)

[Yashp002]

Alright @cmaloney , thanks for clarifying this :D

[picnixz]

I'm going to close this indeed.