[issue38916] Remove array.fromstring() and array.tostring() aliases, deprecated since Python 3.2

STINNER Victor added the comment: The aliases were deprecated since Python 3.2. It's now time to use the newer names. array.array.fromstring() implictly converted Unicode to UTF-8: $ python3 Python 3.7.5 (default, Oct 17 2019, 12:16:48) >>> import array >>> a=array.array('B') >>> a.fromstrin

[issue38916] Remove array.fromstring

miss-islington added the comment: New changeset 21e11383cc59146184da0d69a3f19f004215f9a7 by Miss Islington (bot) in branch '3.7': bpo-38916: Document array.array deprecation (GH-17523) https://github.com/python/cpython/commit/21e11383cc59146184da0d69a3f19f004215f9a7 -- nosy: +miss-i

[issue38916] Remove array.fromstring

Change by miss-islington : -- pull_requests: +17003 pull_request: https://github.com/python/cpython/pull/17525 ___ Python tracker ___ __

[issue38916] Remove array.fromstring

STINNER Victor added the comment: New changeset 0381ea79ac2da03179c8512c581cac588b69cff9 by Victor Stinner in branch '3.8': bpo-38916: Document array.array deprecation (GH-17523) https://github.com/python/cpython/commit/0381ea79ac2da03179c8512c581cac588b69cff9 -- __

[issue38916] Remove array.fromstring

STINNER Victor added the comment: Brett Cannon: "If it was documented as deprecated and raising a deprecation warning then 3.2 is definitely far enough back to warrant removing it." I understood that Brett is in favor of removing it. Raymond Hettinger: "The tostring() method should be handle

[issue38916] Remove array.fromstring

Change by STINNER Victor : -- pull_requests: +17001 pull_request: https://github.com/python/cpython/pull/17523 ___ Python tracker ___ __

[issue38916] Remove array.fromstring

STINNER Victor added the comment: New changeset 0131aba5ae20d704b972ecd2ef0fc6c9e370a1b3 by Victor Stinner in branch 'master': bpo-38916: array.array: remove fromstring() and tostring() (GH-17487) https://github.com/python/cpython/commit/0131aba5ae20d704b972ecd2ef0fc6c9e370a1b3 --

[issue38916] Remove array.fromstring

STINNER Victor added the comment: bpo-38897 removed usage of deprecated array.fromstring() method. Commit in master: https://github.com/python/cpython/commit/386d00cc341b549800776b906bfc6b20ea40c7db -- ___ Python tracker

[issue38916] Remove array.fromstring

Change by STINNER Victor : -- keywords: +patch pull_requests: +16966 stage: -> patch review pull_request: https://github.com/python/cpython/pull/17487 ___ Python tracker ___ _

[issue38916] Remove array.fromstring

STINNER Victor added the comment: I chose to write PR 17487 even if the issue was tagged as "easy (C)", just to make sure that the change is done as soon as possible in the 3.9 dev cycle. -- ___ Python tracker

[issue38916] Remove array.fromstring

STINNER Victor added the comment: > If it was documented as deprecated and raising a deprecation warning then 3.2 > is definitely far enough back to warrant removing it. Exactly. I'm in favor of removing fromstring() and tostring() methods right now, and update 3.7 and 3.8 documentation to m

[issue38916] Remove array.fromstring

Brett Cannon added the comment: > How about note it in the documentation and logging rather than removing them? Yep, docs and raising DeprecationWarning should be good. -- ___ Python tracker ___

[issue38916] Remove array.fromstring

Dong-hee Na added the comment: > The other deprecation in the array module says, "Deprecated since version > 3.3, will be removed in version 4.0". Perhaps this one should have had the > same qualifier. I agree, How about note it in the documentation and logging rather than removing them? -

[issue38916] Remove array.fromstring

Brett Cannon added the comment: > there's no harm to keeping it (it's not broken) ... for now. :) There's always the risk that will change if we keep the code around. > The other deprecation in the array module says, "Deprecated since version > 3.3, will be removed in version 4.0". Perhaps

[issue38916] Remove array.fromstring

Raymond Hettinger added the comment: Thoughts: * The tostring() method should be handled in the same way. * Remediation is easy because from_bytes() is a alias * Still, all removals cause disruption from at least some users * The only real benefit of removing it is a sense of tidiness; otherw

[issue38916] Remove array.fromstring

Brett Cannon added the comment: Although I will admit we have not had a discussion on python-dev about removing stuff that was left for Python 2.7 compatibility, so that discussion should probably occur first before we go ripping stuff out. -- ___

[issue38916] Remove array.fromstring

Brett Cannon added the comment: If it was documented as deprecated and raising a deprecation warning then 3.2 is definitely far enough back to warrant removing it. -- ___ Python tracker

[issue38916] Remove array.fromstring

Dong-hee Na added the comment: For whom are interested in this issue, Please wait until the core developer decides to approve this issue. :) After that, we can review the PR for this issue. Thank you for understanding. -- ___ Python tracker

[issue38916] Remove array.fromstring

Change by Dong-hee Na : -- nosy: +brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue38916] Remove array.fromstring

Change by Dong-hee Na : -- keywords: +easy (C) ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue38916] Remove array.fromstring

Dong-hee Na added the comment: I'd like to tag this issue as an easy issue. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue38916] Remove array.fromstring

New submission from Dong-hee Na : array.fromstring was deprecated at 3.2 IMHO, now we can remove array.fromstring. For my research, there is no usage on the standard library. I 'd like to propose that let's remove array.fromstring from 3.9 -- components: Library (Lib) messages: 357495