[issue32687] wrong meaning of arg in Py_tracefunc doc

Change by Xiang Zhang : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue32687] wrong meaning of arg in Py_tracefunc doc

Xiang Zhang added the comment: New changeset 745e9de7dd9d237d54e92d6e4b469e916fb0352b by Xiang Zhang (Miss Islington (bot)) in branch '2.7': bpo-32687: Fix wrong meaning of args for PyTrace_LINE/CALL in documentation (GH-5361) (GH-5378)

[issue32687] wrong meaning of arg in Py_tracefunc doc

Xiang Zhang added the comment: New changeset 854f0424de389f023b375dfd0b50c34dea29e8f8 by Xiang Zhang (Miss Islington (bot)) in branch '3.6': bpo-32687: Fix wrong meaning of args for PyTrace_LINE/CALL in documentation (GH-5361) (GH-5377)

[issue32687] wrong meaning of arg in Py_tracefunc doc

Change by miss-islington : -- pull_requests: +5219 ___ Python tracker ___

[issue32687] wrong meaning of arg in Py_tracefunc doc

Xiang Zhang added the comment: New changeset 9ed0aee27c249dada410a22fff4325a4a61df36d by Xiang Zhang in branch 'master': bpo-32687: Fix wrong meaning of args for PyTrace_LINE/CALL in documentation (#5361)

[issue32687] wrong meaning of arg in Py_tracefunc doc

Change by miss-islington : -- pull_requests: +5218 ___ Python tracker ___

[issue32687] wrong meaning of arg in Py_tracefunc doc

Change by Xiang Zhang : -- keywords: +patch pull_requests: +5206 stage: -> patch review ___ Python tracker ___

[issue32687] wrong meaning of arg in Py_tracefunc doc

New submission from Xiang Zhang : The meaning of arg for PyTrace_Line and PyTrace_CALL is wrong, it is not always NULL but always Py_None. -- assignee: docs@python components: Documentation messages: 310865 nosy: docs@python, xiang.zhang priority: normal severity: