Mailman 3 March 2013 - docs

Re: [docs] xml.etree.ElementTree.find(all): docs are wrong (issue 11367)
by actonwiley＠gmail.com March 8, 2013

March 8, 2013

http://bugs.python.org/review/11367/

1 0

xml.etree.ElementTree.find(all): docs are wrong (issue 11367)
by actonwiley＠gmail.com March 8, 2013

March 8, 2013

http://bugs.python.org/review/11367/

1 0

sqlite3 cursor object missing attribute documentation
by Eric Williams March 8, 2013

March 8, 2013

Ref: http://docs.python.org/2/library/sqlite3.html#sqlite3.Cursor.fetchall The fetchall() method documentation refers to the arraysize attribute of the cursor object, but the cursor object does not document that attribute or any others. I suggest explicitly listing and documenting cursor object attributes. -- Eric Williams ALS Controls Group, LBL

1 0

[issue17378] Document that ctypes automatically applies byref() when argtypes declares POINTER
by Eli Bendersky March 8, 2013

March 8, 2013

New submission from Eli Bendersky: While playing with ctypes a bit, I noticed a feature that doesn't appear to be documented. Suppose I import the readdir_r function (assuming DIRENT is a correctly declared ctypes.Structure): DIR_p = c_void_p DIRENT_p = POINTER(DIRENT) DIRENT_pp = POINTER(DIRENT_p) readdir_r = lib.readdir_r readdir_r.argtypes = [DIR_p, DIRENT_p, DIRENT_pp] readdir_r.restype = c_int It seems that I can then call it as follows: dirent = DIRENT() result = DIRENT_p() readdir_r(dir_fd, dirent, result) Note that while readdir_r takes DIRENT_p and DIRENT_pp as its second and third args, I pass in just DIRENT and DIRENT_p, accordingly. What I should have done is use byref() on both, but ctypes seems to have some magic applied when argtypes declares pointer types. If I use byref, it still works. However, if I keep the same call and comment out the argtypes declaration, I get a segfault. This behavior of ctypes should be documented. ---------- assignee: docs@python components: Documentation keywords: easy messages: 183661 nosy: docs@python, eli.bendersky priority: normal severity: normal stage: needs patch status: open title: Document that ctypes automatically applies byref() when argtypes declares POINTER type: behavior versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17378> _______________________________________

3 5

[issue10224] Build 3.x documentation using python3.x
by Tshepang Lekhonkhobe March 7, 2013

March 7, 2013

Changes by Tshepang Lekhonkhobe <tshepang(a)gmail.com>: ---------- nosy: +tshepang _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10224> _______________________________________

1 0

[issue10224] Build 3.x documentation using python3.x
by Terry J. Reedy March 7, 2013

March 7, 2013

Terry J. Reedy added the comment: Doc/make.bat assumes that this issue has already been resolved: if "%PYTHON%" EQU "" set PYTHON=..\pcbuild\python Even with '_d' appended, as it should be, that does not work for 3.x. I think that line should be @rem'ed out until it does work. Does anyone mind if I do so? I already suggested on #15605 that a workaround be given until it is no longer needed. ---------- nosy: +terry.reedy _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10224> _______________________________________

1 0

TimedRotatingFileHandler documentation regarding 'Week day' lacking (issue 17376)
by tshepang＠gmail.com March 7, 2013

March 7, 2013

Reviewers: , http://bugs.python.org/review/17376/diff/7548/Doc/library/logging.handlers.… File Doc/library/logging.handlers.rst (right): http://bugs.python.org/review/17376/diff/7548/Doc/library/logging.handlers.… Doc/library/logging.handlers.rst:320: | ``'W<number>'``| Week day (0=Monday) | LGTM http://bugs.python.org/review/17376/diff/7548/Doc/library/logging.handlers.… Doc/library/logging.handlers.rst:326: ``W`` and the number of the day of the week. Monday is 0, Sunday is 6. I think it's enough to just change the text on the table. Should be obvious... the explanation here is redundant. Please review this at http://bugs.python.org/review/17376/ Affected files: Doc/library/logging.handlers.rst diff -r 66d0f6ef2a7f Doc/library/logging.handlers.rst --- a/Doc/library/logging.handlers.rst Thu Feb 28 18:03:16 2013 +0200 +++ b/Doc/library/logging.handlers.rst Thu Mar 07 09:51:33 2013 -0500 @@ -317,11 +317,14 @@ +----------------+-----------------------+ | ``'D'`` | Days | +----------------+-----------------------+ - | ``'W'`` | Week day (0=Monday) | + | ``'W<number>'``| Week day (0=Monday) | +----------------+-----------------------+ | ``'midnight'`` | Roll over at midnight | +----------------+-----------------------+ + When using a rotation based on the day of the week from Monday to Sunday, use + ``W`` and the number of the day of the week. Monday is 0, Sunday is 6. + The system will save old log files by appending extensions to the filename. The extensions are date-and-time based, using the strftime format ``%Y-%m-%d_%H-%M-%S`` or a leading portion thereof, depending on the

1 0

[issue8402] Add a function to escape metacharacters in glob/fnmatch
by Serhiy Storchaka March 7, 2013

March 7, 2013

Serhiy Storchaka added the comment: I think it should be a separate issue. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8402> _______________________________________

1 0

[issue8402] Add a function to escape metacharacters in glob/fnmatch
by Matthew Barnett March 7, 2013

March 7, 2013

Matthew Barnett added the comment: I've attached fnmatch_implementation.py, which is a simple pure-Python implementation of the fnmatch function. It's not as susceptible to catastrophic backtracking as the current re-based one. For example: fnmatch('a' * 50, '*a*' * 50) completes quickly. ---------- nosy: +mrabarnett Added file: http://bugs.python.org/file29343/fnmatch_implementation.py _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8402> _______________________________________

1 0

[issue15465] Improved documentation for C API version info
by Nick Coghlan March 7, 2013

March 7, 2013

New submission from Nick Coghlan <ncoghlan(a)gmail.com>: As far as I can tell, the only mentions of the C API version macros are: 1. In the prose for the stable ABI section (incidentally: this section has a typo in the title) 2. In the documentation for sys.hexversion There should be a clear "API and ABI Versioning" section in the C API docs that covers: PY_LIMITED_API PY_HEX_VERSION PY_MAJOR_VERSION PY_MINOR_VERSION PY_MICRO_VERSION PY_RELEASE_LEVEL PY_RELEASE_SERIAL ---------- assignee: docs@python components: Documentation messages: 166546 nosy: docs@python, ncoghlan priority: normal severity: normal stage: needs patch status: open title: Improved documentation for C API version info type: enhancement _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15465> _______________________________________

3 9