[issue29378] Invalid example in documentation for PyErr_Fetch

Kaeptm Blaubaer added the comment: The error is fixed in Python 3.5.3 documentation. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue29378] Invalid example in documentation for PyErr_Fetch

Kaeptm Blaubaer added the comment: Please don't close the bug until it is fixed in the python 3.5 documentation! -- resolution: not a bug -> status: closed -> open ___ Python tracker __

[issue29378] Invalid example in documentation for PyErr_Fetch

Xiang Zhang added the comment: I can't see any problem with the example either. So I just close this issue for now. But if you still think it gets problems please reopen it and tell your thoughts. -- nosy: +xiang.zhang resolution: -> not a bug stage: -> resolved status: open -> close

[issue29378] Invalid example in documentation for PyErr_Fetch

Kaeptm Blaubaer added the comment: I had no outdated documentation, but the documentation of 3.5. -- resolution: out of date -> status: closed -> open versions: +Python 3.5 ___ Python tracker _

[issue29378] Invalid example in documentation for PyErr_Fetch

Kaeptm Blaubaer added the comment: I had an outdated version of the documentation. -- resolution: -> out of date status: open -> closed ___ Python tracker ___ __

[issue29378] Invalid example in documentation for PyErr_Fetch

Serhiy Storchaka added the comment: The example looks correct to me. Could you please add more information? What example looks correct to you? -- nosy: +serhiy.storchaka ___ Python tracker

[issue29378] Invalid example in documentation for PyErr_Fetch

New submission from Kaeptm Blaubaer: In the example are the pointers to pointers to PyObject too many, because then PyErr_Fetch and PyErr_Restore would get too many pointers to pointers. -- assignee: docs@python components: Documentation messages: 286321 nosy: Kaeptm Blaubaer, docs@pyth