Mailman 3 October 2015 - docs

[issue25123] Logging Documentation - dictConfig disable_existing_loggers
by Robin 01 Oct '15

01 Oct '15

New submission from Robin: logging.config.dictConfig appears to share the same parameter as logging.config.fileConfig - disable_existing_loggers. This parameter is documented for fileConfig but not dictConfig. Suggest update to dictConfig documentation section. ---------- assignee: docs@python components: Documentation messages: 250755 nosy: coderobot, docs@python priority: normal severity: normal status: open title: Logging Documentation - dictConfig disable_existing_loggers type: enhancement versions: Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25123> _______________________________________

3 2

[issue25284] Spec for BaseEventLoop.run_in_executor(executor, callback, *args) is outdated in documentation
by Andrew Svetlov 01 Oct '15

01 Oct '15

Andrew Svetlov added the comment: Fixed in 9a10055e12fa d7d18ef3e05c 1465b18ef4fc ---------- nosy: +asvetlov resolution: -> fixed stage: -> resolved status: open -> closed versions: +Python 3.4, Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25284> _______________________________________

1 0

[issue25275] Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters
by Shreevatsa R 01 Oct '15

01 Oct '15

New submission from Shreevatsa R: Summary: This is about int(u'१२३४') == 1234. At https://docs.python.org/2/library/functions.html and also https://docs.python.org/3/library/functions.html the documentation for class int(x=0) class int(x, base=10) says (respectively): > If x is not a number or if base is given, then x must be a string or Unicode object representing an integer literal in radix base. > If x is not a number or if base is given, then x must be a string, bytes, or bytearray instance representing an integer literal in radix base. If you follow the definition of "integer literal" into the reference (https://docs.python.org/2/reference/lexical_analysis.html#integers and https://docs.python.org/3/reference/lexical_analysis.html#integers respectively), the definitions ultimately involve nonzerodigit ::= "1"..."9" octdigit ::= "0"..."7" bindigit ::= "0" | "1" digit ::= "0"..."9" So it looks like whether the behaviour of int() conforms to its documentation hinges on what "representing" means. Apparently it is some definition under which u'१२३४' represents the integer literal 1234, but it would be great to either clarify the documentation of int() or change its behaviour. ---------- assignee: docs@python components: Documentation, Interpreter Core, Unicode messages: 251915 nosy: docs@python, ezio.melotti, haypo, shreevatsa priority: normal severity: normal status: open title: Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25275> _______________________________________

3 9