Mailman 3 January 2014 - docs

[issue6627] threading.local() does not work with C-created threads
by Nikolaus Rath Jan. 8, 2014

Jan. 8, 2014

Nikolaus Rath added the comment: Here's a patch that (I think) incorporates all the comments. If someone could apply it, that would be great :-). ---------- keywords: +patch versions: +Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5 Added file: http://bugs.python.org/file33361/issue6627.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue6627> _______________________________________

1 0

[issue19273] Update PCbuild/readme.txt
by Zachary Ware Jan. 7, 2014

Jan. 7, 2014

New submission from Zachary Ware: Full title: Update PCbuild/readme.txt to be more accurate, more descriptive, more complete, less repetitive, more audience-aware, and all around, hopefully, better. What started as a simple patch to fix the supported Windows versions list, the legacy build folders list, and a couple other minor factual errors turned into a nearly complete rewrite of the whole file. The changes are too extensive to list out in this message; I'll use Rietveld to point out particular changes and my reasoning for them as soon as I'm able. Also, due to the nature of the changes, it may be simpler to review the changed file itself rather than the patch, so I'll post the patched file as well. At least 90% of these changes also apply to 3.3, but not all; I'd be happy to backport this patch or provide a new patch that strictly addresses factual errors in 3.3, as desired. Thanks, Zach ---------- assignee: docs@python components: Documentation, Windows files: pcbuild_readme.diff keywords: patch messages: 200085 nosy: docs@python, zach.ware priority: normal severity: normal status: open title: Update PCbuild/readme.txt versions: Python 3.4 Added file: http://bugs.python.org/file32148/pcbuild_readme.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue19273> _______________________________________

5 13

[issue20096] Mention modernize and future in Python 2/3 porting HOWTO
by Brett Cannon Jan. 7, 2014

Jan. 7, 2014

New submission from Brett Cannon: https://github.com/mitsuhiko/python-modernize http://python-future.org/ Should also restructure to de-emphasize 2to3 and other approaches. In all honesty it should probably be nearly gutted to just "here are examples of how to write Python 2/3 compatible code", point to appropriate libraries, and be done with it with a minimal mention of 2to3 and 3to2. ---------- assignee: docs@python components: Documentation messages: 207103 nosy: brett.cannon, docs@python priority: normal severity: normal status: open title: Mention modernize and future in Python 2/3 porting HOWTO versions: Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20096> _______________________________________

4 4

[issue20150] API change in string formatting with :s option should be documented in What's New.
by Eric V. Smith Jan. 6, 2014

Jan. 6, 2014

Eric V. Smith added the comment: Oops, I missed the "should be documented" part of your message. That's true, and I'll leave this open. But I'll change it to a doc request and assign it accordingly. ---------- assignee: eric.smith -> docs@python components: +Documentation -Interpreter Core nosy: +docs@python resolution: invalid -> status: closed -> open title: API breakage in string formatting with :s option -> API change in string formatting with :s option should be documented in What's New. _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20150> _______________________________________

1 0

Why not have a complete python language reference manual describes?
by Xiaofeng Tan Jan. 6, 2014

Jan. 6, 2014

Dear Python developers, I am a Chinese college student, I want to learn Python programming language, but I can't find a documentation about the Python for a complete description in your website. Python is so popular in China. I am looking forward to your website can provide Python manual. The same as PHP manual. Thanks! Form Huanggang Normal University, Huanggang Hubei China.

1 0

[issue20141] Argument Clinic: broken support for 'O!'
by Serhiy Storchaka Jan. 6, 2014

Jan. 6, 2014

New submission from Serhiy Storchaka: First, the documentation says that syntax for 'O!' conversion is object(type='name_of_Python_type'), but actually the type argument should be the name of C structure which represents Python type. I.e. object(type='list') is rejected, and object(type='PyList_Type') is accepted. Second, from this declaration /*[clinic] module spam spam.ham items: object(type='PyList_Type') / [clinic]*/ Argument Clinic generates following parsing code: if (!PyArg_ParseTuple(args, "O!:ham", PyList_Type, &items)) goto exit; It is wrong, should be &PyList_Type. ---------- assignee: docs@python components: Build, Documentation messages: 207430 nosy: docs@python, larry, serhiy.storchaka priority: release blocker severity: normal status: open title: Argument Clinic: broken support for 'O!' type: crash versions: Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20141> _______________________________________

2 4

[issue20134] typo: s/coping/copying/
by INADA Naoki Jan. 6, 2014

Jan. 6, 2014

New submission from INADA Naoki: http://docs.python.org/3.3/library/unittest.mock-examples.html#coping-with-… "coping" should be "copying"? ---------- assignee: docs@python components: Documentation messages: 207409 nosy: docs@python, naoki priority: normal severity: normal status: open title: typo: s/coping/copying/ versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20134> _______________________________________

2 2

[issue20135] mutate list
by R. David Murray Jan. 6, 2014

Jan. 6, 2014

R. David Murray added the comment: Both of these are FAQs, but to my surprise there don't seem to be answers to them in the FAQ list. We should add some. Yes, both of these behaviors is intentional. The first is an important part of the language design: 'variable' names are just pointers to objects, so x and y point to the same object. The second is the same issue combined with another design feature: the objects on the right side of the = in a def statement are evaluated/created at the time the def statement is executed, not at the time the function is called. So 'n' points to the same object every time the function is called. I'm going to leave this open until someone either points me to the FAQ entries I missed, or we add them. ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python, r.david.murray versions: +Python 2.7, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20135> _______________________________________

1 0

[issue20110] Misleading word used for __annotations__
by Claudiu.Popa Jan. 2, 2014

Jan. 2, 2014

New submission from Claudiu.Popa: The documentation for `__annotations__` specify that the dict contains the parameter names ``or`` the return, but this is misleading, because `return` exists even if the parameter keys are present. ---------- assignee: docs@python components: Documentation files: doc_annotation.patch keywords: patch messages: 207183 nosy: Claudiu.Popa, docs@python priority: normal severity: normal status: open title: Misleading word used for __annotations__ versions: Python 3.4 Added file: http://bugs.python.org/file33297/doc_annotation.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20110> _______________________________________

2 1

[issue17282] document the defaultTest parameter to unittest.main()
by Chris Jerdonek Jan. 2, 2014

Jan. 2, 2014

New submission from Chris Jerdonek: This issue is to document the defaultTest parameter to unittest.main(): http://docs.python.org/dev/library/unittest.html#unittest.main Note that it is not enough simply to say that *defaultTest* is a "default test name or iterable of test names." The documentation should also say when *defaultTest* is used based on the value of the *module* and *argv* arguments, etc. This issue is an offshoot of issue 15132. ---------- assignee: docs@python components: Documentation keywords: easy messages: 182839 nosy: chris.jerdonek, docs@python, ezio.melotti, michael.foord priority: normal severity: normal stage: needs patch status: open title: document the defaultTest parameter to unittest.main() type: enhancement versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17282> _______________________________________

5 5