New submission from Sandro Tosi <sandro.tosi(a)gmail.com>:
Hello,
given I can't fully comprehend the user request (sent on docs@ as of http://mail.python.org/pipermail/docs/2011-September/005791.html), I'm just echoing it :
>>>
recently I embedded Python into one of my applications, which included
some string parsing.
In my opinion the doc page about parsing arguments
(http://docs.python.org/c-api/arg.html) is missing the information, that
you must not free the returned const char *, like e.g. said here
(http://docs.python.org/c-api/string.html#PyString_AsString).
It was quite confusing for my first, so I would suggest adding this tiny
bit of information.
<<<
----------
assignee: docs@python
components: Documentation
messages: 146687
nosy: docs@python, sandro.tosi
priority: normal
severity: normal
stage: needs patch
status: open
title: Clarification needed in C API arg parsing
versions: Python 2.7, Python 3.2, Python 3.3
_______________________________________
Python tracker <report(a)bugs.python.org>
<http://bugs.python.org/issue13302>
_______________________________________
New submission from maniram maniram <maniandram01(a)gmail.com>:
In the Python 3 docs for the raise statement, http://docs.python.org/py3k/reference/simple_stmts.html#the-raise-statement… docs say "If no exception is active in the current scope, a TypeError exception is raised indicating that this is an error (if running under IDLE, a queue.Empty exception is raised instead).
This is wrong in Python 3 because raise raises a RuntimeError and IDLE does the same (does not raise a queue.Empty Exception).
The text should be "If no exception is active in the current scope, a RuntimeError exception is raised indicating that this is an error."
----------
assignee: docs@python
components: Documentation
messages: 150382
nosy: docs@python, maniram.maniram
priority: normal
severity: normal
status: open
title: Docs in Python 3:raise statement mistake
versions: Python 3.2
_______________________________________
Python tracker <report(a)bugs.python.org>
<http://bugs.python.org/issue13683>
_______________________________________
