This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: [array doc] Possible missing deprecation warnings?
Type: enhancement Stage:
Components: Documentation, Library (Lib) Versions: Python 3.10, Python 3.9, Python 3.8
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, mark
Priority: normal Keywords:

Created on 2016-06-07 19:55 by mark, last changed 2022-04-11 14:58 by admin.

Messages (1)
msg267738 - (view) Author: Mark Summerfield (mark) * Date: 2016-06-07 19:55
In the docs for the array module:
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()?)
Date User Action Args
2022-04-11 14:58:32adminsetgithub: 71446
2020-11-26 21:58:25iritkatrielsettitle: Possible missing deprecation warnings? -> [array doc] Possible missing deprecation warnings?
components: + Library (Lib)
versions: + Python 3.8, Python 3.9, Python 3.10, - Python 3.6
2016-06-07 19:55:04markcreate