The doc of `bytes.maketrans()` and `bytearray.maketrans()` should also say `bytearray.translate()`

[hyperkai]

The doc of bytes.maketrans() and bytearray.maketrans() says only bytes.translate() as shown below even though bytearray.translate() also works:

This static method returns a translation table usable for bytes.translate() that will map each character ...

So, the doc of bytes.maketrans() and bytearray.maketrans() should also say bytearray.translate() as shown below:

This static method returns a translation table usable for bytes.translate() and bytearray.translate() that will map each character ...

Linked PRs

• gh-137235 : add bytearray as usable to bytes.maketrans and bytearray.maketrans. #138255

[StanFromIreland]

There are many occurrences of this on the page, both link to the same text, I think this will unnecessarily extend the sections.

[terryjreedy]

I disagree. This issue is definitely not 'invalid' (this label is used for spam). And this is the only reference to bytes.translate on the page. (bytes-like object what has many occuurences.) To be concise, the text could be bytearray or bytes.translate, with only the latter referenced.

The bytes/bytearray.translate entry refers to bytes.maketrans. I see no need to add bytearray.maketrans as the latter is essentially the same function. (Since it is a static function with the same return however accessed, I would not have added what is essentially a synonym.)

[StanFromIreland]

@terryjreedy I closed it because this almost identical issue was closed: #137259

As for the many instances, I meant that all bytes/bytearray functions that referenced another reference only the bytes variant.