Mailman 3 May 2014 - docs

Downloads not available
by Wiebke Walbaum 18 May '14

18 May '14

Hello, I just wanted to download the Python 3.4 1rc1 Documentation, but the links all lead to 404 Not Found :( It would be nice if you could fix that. Yours sincerely Wiebke --- Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz ist aktiv. http://www.avast.com

1 0

PDF / Zip documentation files not found from https://docs.python.org/3/download.html
by Tony O'Brien 18 May '14

18 May '14

Thanks for the software. Fantastic Tony

1 0

Feature request: make searching for "@" return information on decorators
by Will Marler 16 May '14

16 May '14

TL;DR: see the subject line I'm new to Python and was reading code that used this: @property def ... and I didn't know what it meant. I looked in the python.org docs for "@" and "@property" and didn't get any results, so I turned to Google and found a good page on stackoverflow about how "@property" worked ( http://stackoverflow.com/questions/17330160/python-how-does-the-property-de… ). However, I still did not understand "@". I eventually asked a colleague (I try to RTFM before asking), and he said "oh ya, that's a decorator." Once I knew that "@" = "decorator," I could search for "decorator" in the docs and get useful results. In fact, I found a LOT of great results; this isn't a request for more information on decorators :). I probably spent 15-20 minutes before learning @ = decorator, and I'm sure this is something that plagues other newbies. Can the docs (or search functionality) be updated so someone searching on "@" as a single search term will get information on decorators? Search results could include a direction to the decorator entry in the glossary?, the function/class definition pages, etc. Thanks, Will

1 0

[issue21488] codecs.encode/decode documentation inconsistency
by Brad Aylsworth 14 May '14

14 May '14

New submission from Brad Aylsworth: The documentation page for codecs (https://docs.python.org/2/library/codecs.html) shows keyword arguments for codecs.encode and codecs.decode, but they throw an error if keyword arguments are used. codecs.decode.__doc__ reports 'decode(obj, [encoding[,errors]]) -> object. This happens on both 2.7.6 and 3.4.0. ---------- assignee: docs@python components: Documentation messages: 218380 nosy: Ouaouaron, docs@python priority: normal severity: normal status: open title: codecs.encode/decode documentation inconsistency type: resource usage versions: Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue21488> _______________________________________

6 14

[issue21347] Don't use a list argument together with shell=True in subprocess' docs
by akira 14 May '14

14 May '14

New submission from akira: *Popen(["something"], shell=True)* works but it is similar to *Popen(["something", "arg"], shell=True)* that passes "arg" to /bin/sh on POSIX systems instead of "something". It is best to always use a string if `shell=True` is necessary. It is a common confusion #20344, msg98732, #7839 http://stackoverflow.com/questions/21029154/understanding-python-subprocess… http://stackoverflow.com/questions/20787712/start-openoffice-process-with-p… http://stackoverflow.com/questions/17880847/python-subprocess-error-in-usin… http://stackoverflow.com/questions/17226912/why-does-simple-echo-in-subproc… http://stackoverflow.com/questions/15109665/subprocess-call-using-string-vs… http://stackoverflow.com/questions/20128114/pythons-subprocess-does-not-int… http://stackoverflow.com/questions/16840427/python-on-linux-subprocess-pope… ... ---------- assignee: docs@python components: Documentation files: docs-subprocess-dont_use_list_with_shell_true.patch keywords: patch messages: 217136 nosy: akira, docs@python priority: normal severity: normal status: open title: Don't use a list argument together with shell=True in subprocess' docs type: behavior versions: Python 3.5 Added file: http://bugs.python.org/file35026/docs-subprocess-dont_use_list_with_shell_t… _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue21347> _______________________________________

5 5

Re: [docs] codecs.encode/decode documentation inconsistency (issue 21488)
by victor.stinner＠gmail.com 14 May '14

14 May '14

On 2014/05/14 13:16:36, berkerpeksag wrote: > The errors argument already documented in the next paragraph: Oh ok, sorry. So your patch is good. http://bugs.python.org/review/21488/

1 0

Re: [docs] codecs.encode/decode documentation inconsistency (issue 21488)
by berker.peksag＠gmail.com 14 May '14

14 May '14

On 2014/05/14 11:21:46, haypo wrote: > http://bugs.python.org/review/21488/diff/11863/Doc/library/codecs.rst > File Doc/library/codecs.rst (right): > > http://bugs.python.org/review/21488/diff/11863/Doc/library/codecs.rst#newco… > Doc/library/codecs.rst:29: encoding is ``utf-8``. > You should also mention the default error handler: > > The default *encoding* is ``'utf-8'`` and the default *error* handler is > ``'strict'``. > > http://bugs.python.org/review/21488/diff/11863/Doc/library/codecs.rst#newco… > Doc/library/codecs.rst:40: encoding is ``utf-8``. > The default *encoding* is ``'utf-8'`` and the default *error* handler is > ``'strict'``. The errors argument already documented in the next paragraph: "The default error handler is strict meaning that encoding errors raise [...]" https://docs.python.org/3.5/library/codecs.html#codecs.encode Do you want me to add the "and the default *error* handler is ``'strict'``" part anyway? Will update the patch for style changes. Thanks for the review, Victor. http://bugs.python.org/review/21488/

1 0

codecs.encode/decode documentation inconsistency (issue 21488)
by victor.stinner＠gmail.com 14 May '14

14 May '14

http://bugs.python.org/review/21488/diff/11863/Doc/library/codecs.rst File Doc/library/codecs.rst (right): http://bugs.python.org/review/21488/diff/11863/Doc/library/codecs.rst#newco… Doc/library/codecs.rst:29: encoding is ``utf-8``. You should also mention the default error handler: The default *encoding* is ``'utf-8'`` and the default *error* handler is ``'strict'``. http://bugs.python.org/review/21488/diff/11863/Doc/library/codecs.rst#newco… Doc/library/codecs.rst:40: encoding is ``utf-8``. The default *encoding* is ``'utf-8'`` and the default *error* handler is ``'strict'``. http://bugs.python.org/review/21488/

1 0

Python doc google search results 3.0 vs 2.6
by Christopher J. White 13 May '14

13 May '14

Hi folks, Not sure if this is a bug or just a weirdness with google. When I do a google search such as "python subprocess", the first result that comes back looks like the following: Showing results for python subprocess 17.1. /subprocess/ - /Python/ 3.4.0 documentation <https://docs.python.org/2/library/subprocess.html> https://docs.*python*.org/2/library/*subprocess*.html The /subprocess/ module allows you to spawn new processes, connect to their input/output/error pipes, and obtain their return codes. This module intends to ... Notice the header says 3.4.0 but the link goes to python.org/2, and in fact when you click you are looking at the 2.x version docs. I noticed this crop up about a week ago, I see it on lots of searches. I don't see any reference to 3.4.0 in the source for that file, so I'm not sure how it could be a python.org issue, but I'm not a search engine expert. ...cj

2 1

Hey.
by alex＠codecondo.com 13 May '14

13 May '14

Hey guys, was just wondering whether it's possible to have one of my articles to be added to the official Python Wiki? http://codecondo.com/10-ways-to-learn-python/ it's been getting a lot of positive feedback lately, and looks like it's helping a lot of beginners to get started. I hand curated that list a couple of weeks ago, would definitely be cool to see it as a reference for newcomers who begin their journey through the Wiki. peace, Alex

2 1