Mailman 3 September 2013 - docs

[issue18553] os.isatty() is not Unix only
by Senthil Kumaran 19 Sep '13

19 Sep '13

Senthil Kumaran added the comment: Fixed now. Ascertained myself by doing hg diff -r tip^ -U 10 on local commits before pushing. :-) ---------- status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18553> _______________________________________

1 0

[issue18553] os.isatty() is not Unix only
by Roundup Robot 19 Sep '13

19 Sep '13

Roundup Robot added the comment: New changeset 2b7f11ba871c by Senthil Kumaran in branch '3.3': Correcting the mistake in 14ba90816930 http://hg.python.org/cpython/rev/2b7f11ba871c New changeset e839e524a7d5 by Senthil Kumaran in branch 'default': Correcting the mistake in 678e3c0d2d99 http://hg.python.org/cpython/rev/e839e524a7d5 ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18553> _______________________________________

1 0

[issue18553] os.isatty() is not Unix only
by Senthil Kumaran 19 Sep '13

19 Sep '13

Senthil Kumaran added the comment: Georg: Thanks for spotting. I feel bad for the mistake. I shall correct it. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18553> _______________________________________

1 0

Small problem with the pop function reference
by tarpeyjb＠gmail.com 19 Sep '13

19 Sep '13

In the table at http://docs.python.org/3/library/stdtypes.html#mutable-sequence-types s.pop([i]) is shown, which is incorrect. s.pop(i) is the proper example: >>> s = [1, 2, 3] >>> s.pop([0]) Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: 'list' object cannot be interpreted as an integer >>> s = [1, 2, 3] >>> s.pop(0) 1

1 0

[issue19039] sphinx search, result sorting
by Thomas Guettler 18 Sep '13

18 Sep '13

New submission from Thomas Guettler: If you search for "printf" in the docs you get this result: http://docs.python.org/3.3/search.html?q=printf&check_keywords=yes&area=def… Please have a look at the first results. I guess most people don't want to see docs about "PyOS_snprintf" Most people want to see this: http://docs.python.org/3.3/library/stdtypes.html?highlight=printf#printf-st… The good page (stdtypes.html) is the fourth search result. And this page is huge. Unfortunately the link from the search result does not link to the section, it links to the top of the page. Since "printf" is in the heading, sphinx should be able to create a link to the relevant section in this page (in this example #printf-style-string-formatting). Thank you ---------- assignee: docs@python components: Documentation messages: 197963 nosy: docs@python, guettli priority: normal severity: normal status: open title: sphinx search, result sorting _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue19039> _______________________________________

3 3

[issue18553] os.isatty() is not Unix only
by Georg Brandl 17 Sep '13

17 Sep '13

Georg Brandl added the comment: Senthil: your 3.3->default merge removed the Availability from fpathconf(). ---------- nosy: +georg.brandl status: closed -> open _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18553> _______________________________________

1 0

CSV nit-pick
by Sullivan, Jon Paul 16 Sep '13

16 Sep '13

The intro to the CSV module says there is no standard for a CSV file: http://docs.python.org/2/library/csv.html. Although not an actual standard, http://tools.ietf.org/html/rfc4180 defines the format of CSV files for the text/csv mime-type, and should likely be referenced and adhered to by the CSV code. Thanks, *: JonPaul.Sullivan(a)hp.com :) Cloud Services - @hpcloud *: +353 (91) 75 4169 Postal Address: Hewlett-Packard Galway Limited, Ballybrit Business Park, Galway. Registered Office: Hewlett-Packard Galway Limited, 63-74 Sir John Rogerson's Quay, Dublin 2. Registered Number: 361933 The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated, you should consider this message and attachments as "HP CONFIDENTIAL".

1 0

[issue9694] argparse required arguments displayed under "optional arguments"
by paul j3 16 Sep '13

16 Sep '13

Changes by paul j3 <ajipanca(a)gmail.com>: ---------- nosy: +paul.j3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9694> _______________________________________

1 0

Re: [docs] Improve the documentation in fcntl module (issue 18985)
by sky.kok＠speaklikeaking.com 15 Sep '13

15 Sep '13

Reviewers: ezio.melotti, http://bugs.python.org/review/18985/diff/9247/Modules/fcntlmodule.c File Modules/fcntlmodule.c (right): http://bugs.python.org/review/18985/diff/9247/Modules/fcntlmodule.c#newcode… Modules/fcntlmodule.c:120: char buf[IOCTL_BUFSZ+1]; /* argument plus NULL byte */ On 2013/09/13 23:10:07, ezio.melotti wrote: > http://en.wikipedia.org/wiki/Null_character Ah, sorry about that. http://bugs.python.org/review/18985/diff/9247/Modules/fcntlmodule.c#newcode… Modules/fcntlmodule.c:422: and ioctl() Unix routines. File descriptors can be obtained with the \n\ On 2013/09/13 23:10:07, ezio.melotti wrote: > This sentence might be clearer. Are they all Unix routines? Are they available > on all systems except flock()? On what systems is flock() available? It is not clear why on some system flock is not available natively. But the manual (http://linux.about.com/library/cmd/blcmdl2_flock.htm) and the comment inside this file says: A version of flock(2), possibly implemented in terms of fcntl(2), appears on most Unices. & Perform the lock operation opt on file descriptor fd. See the Unix \n\ manual page for flock(3) for details. (On some systems, this function is\n\ emulated using fcntl().) Lockf is somewhat similar with flock. On Linux, lockf() is just an interface on top of fcntl(2) locking. Many other systems implement lockf() in this way, but note that POSIX.1-2001 leaves the relationship between lockf() and fcntl(2) locks unspecified. So in most (all?) cases, ioctl and fcntl are unix routines. But in most (all?) cases, lockf is emulated around fcntl. And in some cases, flock is emulated around fcntl, and in other cases, flock comes natively. Please review this at http://bugs.python.org/review/18985/ Affected files: Modules/fcntlmodule.c diff -r aff959a3ba13 Modules/fcntlmodule.c --- a/Modules/fcntlmodule.c Sun Sep 08 18:44:40 2013 -0500 +++ b/Modules/fcntlmodule.c Mon Sep 09 18:21:53 2013 +0800 @@ -80,8 +80,8 @@ "fcntl(fd, opt, [arg])\n\ \n\ Perform the requested operation on file descriptor fd. The operation\n\ -is defined by op and is operating system dependent. These constants are\n\ -available from the fcntl module. The argument arg is optional, and\n\ +is defined by opt and is operating system dependent. The possible values of\n\ +opt are available from the fcntl module. The argument arg is optional, and\n\ defaults to 0; it may be an int or a string. If arg is given as a string,\n\ the return value of fcntl is a string of that length, containing the\n\ resulting value put in the arg buffer by the operating system. The length\n\ @@ -104,7 +104,7 @@ whereas the system expects it to be a 32bit bit field value regardless of it being passed as an int or unsigned long on various platforms. See the termios.TIOCSWINSZ constant across - platforms for an example of thise. + platforms for an example of this. If any of the 64bit platforms ever decide to use more than 32bits in their unsigned long ioctl codes this will break and need @@ -117,7 +117,7 @@ char *str; Py_ssize_t len; int mutate_arg = 1; - char buf[IOCTL_BUFSZ+1]; /* argument plus NUL byte */ + char buf[IOCTL_BUFSZ+1]; /* argument plus NULL byte */ if (PyArg_ParseTuple(args, "O&Iw*|i:ioctl", conv_descriptor, &fd, &code, @@ -306,9 +306,9 @@ } PyDoc_STRVAR(flock_doc, -"flock(fd, operation)\n\ +"flock(fd, opt)\n\ \n\ -Perform the lock operation op on file descriptor fd. See the Unix \n\ +Perform the lock operation opt on file descriptor fd. See the Unix \n\ manual page for flock(3) for details. (On some systems, this function is\n\ emulated using fcntl().)"); @@ -418,9 +418,9 @@ PyDoc_STRVAR(module_doc, "This module performs file control and I/O control on file \n\ -descriptors. It is an interface to the fcntl() and ioctl() Unix\n\ -routines. File descriptors can be obtained with the fileno() method of\n\ -a file or socket object."); +descriptors. It is an interface to the fcntl(), flock() (on some systems) \n\ +and ioctl() Unix routines. File descriptors can be obtained with the \n\ +fileno() method of a file or socket object."); /* Module initialisation */

1 0

[issue18958] Exception('No JSON object could be decoded') when parsing a valid JSON
by Anoop Thomas Mathew 15 Sep '13

15 Sep '13

Anoop Thomas Mathew added the comment: Patch for BOM signature documentation in json.loads ---------- keywords: +patch nosy: +Anoop.Thomas.Mathew Added file: http://bugs.python.org/file31764/json_BOM_signature_documentation.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18958> _______________________________________

1 0