[array doc] Possible missing deprecation warnings?

[mark-summerfield]

BPO	27259
Nosy	@mark-summerfield

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2016-06-07.19:55:04.421>
labels = ['3.8', '3.9', '3.10', 'type-feature', 'library', 'docs']
title = '[array doc]  Possible missing deprecation warnings?'
updated_at = <Date 2020-11-26.21:58:25.878>
user = 'https://github.com/mark-summerfield'

bugs.python.org fields:

activity = <Date 2020-11-26.21:58:25.878>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Library (Lib)']
creation = <Date 2016-06-07.19:55:04.421>
creator = 'mark'
dependencies = []
files = []
hgrepos = []
issue_num = 27259
keywords = []
message_count = 1.0
messages = ['267738']
nosy_count = 2.0
nosy_names = ['mark', 'docs@python']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue27259'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

[mark-summerfield]

In the docs for the array module:
https://docs.python.org/dev/library/array.html#module-array
Note 1 in the table of type codes says that the 'u' type is deprecated and will go in Python 4.0.

Since the array.fromunicode() and array.tounicode() methods depend on type code 'u' shouldn't they also be marked as deprecated?

If people use the 'u' type code maybe it would be helpful to provide an example of how to store unicode chars in an array.array? (Presumably they'd use type code 'L' and use ord() and chr()?)

[aisk]

Hi, the 'w' typecode was added in #105242, and array.fromunicode / array.tounicode support it, so we should keep them. We can also use the 'w' typecode to store Unicode.

So I think we can close this issue as completed.