[issue3565] array documentation, method names not 3.x-compliant

Matt Giuca added the comment: There are still some inconsistencies in the documentation (in particular, incorrectly using the word "string" to refer to a bytes object, which made sense in Python 2 but not 3), which I fixed in my doc-only.patch file that's coming up to its third birthday. Mos

[issue3565] array documentation, method names not 3.x-compliant

Antoine Pitrou added the comment: > Is there still any idea/intention of renaming .from/.tounicode to > .from/.tostring? That would have to be done at least one version with > the 'string' names absent, and would have little gain as 'unicode' is > clear. Indeed, not only it would bring little b

[issue3565] array documentation, method names not 3.x-compliant

Éric Araujo added the comment: It was Antoine in fa8b57f987c5, for #8990. -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs

[issue3565] array documentation, method names not 3.x-compliant

Terry J. Reedy added the comment: In 3.2, a change *was* committed (by who?) but not recorded here: .from/.tostring were renamed .from/.tobytes and kept as deprecated aliases. Is there anything more to this issue other than removing the deprecated aliases in 3.3 (which could be done now if tha

[issue3565] array documentation, method names not 3.x-compliant

Changes by Éric Araujo : -- assignee: -> d...@python nosy: +d...@python stage: unit test needed -> patch review title: array documentation, method names not 3.0 compliant -> array documentation, method names not 3.x-compliant versions: +Python 2.7, Python 3.2 _