Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PyArg_Parse* should deprecate 'u' and 'z' family. #77376

Closed
methane opened this issue Apr 1, 2018 · 6 comments
Closed

PyArg_Parse* should deprecate 'u' and 'z' family. #77376

methane opened this issue Apr 1, 2018 · 6 comments
Labels
3.7 (EOL) end of life 3.8 only security fixes docs Documentation in the Doc dir

Comments

@methane
Copy link
Member

methane commented Apr 1, 2018

BPO 33195
Nosy @methane, @serhiy-storchaka, @miss-islington
PRs
  • bpo-33195: Doc: Deprecate Py_UNICODE in c-api/arg #6329
  • [3.7] bpo-33195: Doc: Deprecate Py_UNICODE in c-api/arg (GH-6329) #6369
  • [3.6] bpo-33195: Doc: Deprecate Py_UNICODE in c-api/arg (GH-6329) #6382
    		•

    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 = <Date 2018-04-04.08:43:07.197>
created_at = <Date 2018-04-01.05:26:13.851>
labels = ['3.7', '3.8', 'docs']
title = "PyArg_Parse* should deprecate 'u' and 'z' family."
updated_at = <Date 2018-04-05.09:08:51.292>
user = 'https://github.com/methane'

    bugs.python.org fields:

    activity = <Date 2018-04-05.09:08:51.292>
actor = 'methane'
assignee = 'docs@python'
closed = True
closed_date = <Date 2018-04-04.08:43:07.197>
closer = 'methane'
components = ['Documentation']
creation = <Date 2018-04-01.05:26:13.851>
creator = 'methane'
dependencies = []
files = []
hgrepos = []
issue_num = 33195
keywords = ['patch']
message_count = 6.0
messages = ['314761', '314765', '314865', '314919', '314921', '314971']
nosy_count = 4.0
nosy_names = ['methane', 'docs@python', 'serhiy.storchaka', 'miss-islington']
pr_nums = ['6329', '6369', '6382']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue33195'
versions = ['Python 3.7', 'Python 3.8']
    @methane
    Copy link
    Member Author

    methane commented Apr 1, 2018

    https://docs.python.org/3/c-api/arg.html

    Py_UNICODE usage is not deprecated in this document.
    Before thinking about raising warning, deprecate it in document first.

    But... from when? Can I backport the "deprecated" doc to 3.6 or 3.5?

    @methane methane added 3.7 (EOL) end of life 3.8 only security fixes labels Apr 1, 2018
    @methane methane added the docs Documentation in the Doc dir label Apr 1, 2018
    @serhiy-storchaka
    Copy link
    Member

    See also bpo-24009. We should get rid of using these units in the stdlib.

    I'm not sure about deprecating Py_BuildValue() units right now. They can be redefined in terms of wchar_t, and they are already implemented with PyUnicode_FromWideChar().

    @methane
    Copy link
    Member Author

    methane commented Apr 3, 2018

    OK, I replaced Py_UNICODE with wchar_t in Py_BuildValue document.

    @methane
    Copy link
    Member Author

    methane commented Apr 4, 2018

    New changeset 42ec190 by INADA Naoki in branch 'master':
    bpo-33195: Doc: Deprecate Py_UNICODE in c-api/arg (GH-6329)
    42ec190

    @miss-islington
    Copy link
    Contributor

    New changeset b8fc2d6 by Miss Islington (bot) in branch '3.7':
    bpo-33195: Doc: Deprecate Py_UNICODE in c-api/arg (GH-6329)
    b8fc2d6

    @methane methane closed this as completed Apr 4, 2018
    @methane
    Copy link
    Member Author

    methane commented Apr 5, 2018

    New changeset 29bc6f6 by INADA Naoki in branch '3.6':
    bpo-33195: Doc: Deprecate Py_UNICODE in c-api/arg (GH-6329)
    29bc6f6

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Assignees
    No one assigned
    Labels
    3.7 (EOL) end of life 3.8 only security fixes docs Documentation in the Doc dir
    Projects
    None yet
    Milestone
    No milestone
    Development

    No branches or pull requests
    3 participants
    @methane @serhiy-storchaka @miss-islington