Mailman 3 November 2015 - docs

ePub Book Corrupt
by docneogi Nov. 12, 2015

Nov. 12, 2015

Hi, this is to bring to your notice that the EPUB book available on https://docs.python.org/3/download.html <https://docs.python.org/3/download.html> for download is corrupt. I use OSX El Capitan. Kindly see to the problem. and if possible when the problem is rectified if I could be kindly notified so that i may download the EPUB book for my personal reference. Warm Regards, Dr. S Neogi

2 1

[issue25603] spelling mistake - 26.1 typing
by Matthias welp Nov. 12, 2015

Nov. 12, 2015

New submission from Matthias welp: Almost at the end of the page, under Usage of Typing.NamedTuple(...), this code snippet occurs: `Employee = typing.NamedTuple('Employee', [('name', str), 'id', int)])`. Unfortunately, this has an error in its parenthesis. This can easily be fixed by adding an opening bracket before the `'id'`-part, as seen here: `Employee = typing.NamedTuple('Employee', [('name', str), ('id', int)])`. ---------- assignee: docs@python components: Documentation messages: … [View More]

3 2

https://docs.python.org/3.5/whatsnew/3.5.html
by keith.briggs＠bt.com Nov. 12, 2015

Nov. 12, 2015

> Objects from random<https://docs.python.org/3.5/library/random.html#module-random> module now use two times less memory on 64-bit builds How can you use "two times less memory"? Wouldn't that make the usage negative? Perhaps "half as much memory" was meant? Keith

2 1

misspelling on website
by Igor Zhun Nov. 12, 2015

Nov. 12, 2015

Hello everybody On page "What’s New In Python 3.6" ( https://docs.python.org/3.6/whatsnew/3.6.html) There is text: datetime.*stftime* and date.*stftime* Maybe it should be: datetime.st*r*ftime and date.st*r*ftime (r are missing twice) Is it OK? Best regards, Igor Zhun

2 1

[issue25570] urllib.request > Request.add_header("abcd", "efgh") fails with character ":" in first parameter string
by Martin Panter Nov. 9, 2015

Nov. 9, 2015

Martin Panter added the comment: Hmm, I wonder if that OpenerDirector example is a bit obscure. Normally you would use the default urlopen() to set User-Agent, without resorting to a custom OpenerDirector. In my patch: * Included “User-Agent header _value_” in the “headers” parameter description * Linked to <https://docs.python.org/dev/howto/urllib2.html> from examples section * Added add_header("User-Agent", ...) example with made-up custom value Let me know what you think (if … [View More]

1 0

Re: [docs] Remove “Content-Type: application/x-www-form-urlencoded; charset” advice (issue 25576)
by vadmium+py＠gmail.com Nov. 9, 2015

Nov. 9, 2015

Reviewers: r.david.murray, http://bugs.python.org/review/25576/diff/15901/Doc/library/urllib.request.r… File Doc/library/urllib.request.rst (right): http://bugs.python.org/review/25576/diff/15901/Doc/library/urllib.request.r… Doc/library/urllib.request.rst:1245: >>> with urllib.request.urlopen("http://requestb.in/xrbl82xr", data) as f: On 2015/11/08 18:24:56, r.david.murray wrote: > We lose something from the example no longer showing a use of add_header. Is > there any other … [View More]header we could add that would make sense in context? I don't > think it is a big deal, though. Nothing immediately comes to mind for this particular example. It might be better to illustrate one concept per example, rather than adding in unrelated headers at the same time. There is already an example at line 1209 setting Referer with add_header(). Some more options: * Perhaps there should be a link to <https://docs.python.org/dev/howto/urllib2.html#headers>, which has example code for setting User-Agent via the Request constructor parameter. * In my patch at Issue 23360 I proposed setting the Content-Type in the examples where data is not in urlencoded format, although again using the constructor rather than add_header(). * Perhaps we can resolve Issue 25570 with an example setting User-Agent via add_header(). Please review this at http://bugs.python.org/review/25576/ Affected files: Doc/library/urllib.parse.rst Doc/library/urllib.request.rst Lib/urllib/request.py # HG changeset patch # Parent 4df1eaecb506507e5d613f8601b48057e7f328a8 Remove advice about setting charset with application/x-www-form-urlencoded No charset parameter is standardized for this Content-Type value. Also clarify that urlencode() outputs ASCII. diff -r 4df1eaecb506 -r 6ff71efb3b5b Doc/library/urllib.parse.rst --- a/Doc/library/urllib.parse.rst Sat Nov 07 03:15:32 2015 +0000 +++ b/Doc/library/urllib.parse.rst Sat Nov 07 08:36:34 2015 +0000 @@ -535,10 +535,11 @@ errors=None, quote_via=quote_plus) Convert a mapping object or a sequence of two-element tuples, which may - contain :class:`str` or :class:`bytes` objects, to a "percent-encoded" - string. If the resultant string is to be used as a *data* for POST - operation with :func:`~urllib.request.urlopen` function, then it should be - properly encoded to bytes, otherwise it would result in a :exc:`TypeError`. + contain :class:`str` or :class:`bytes` objects, to a percent-encoded ASCII + text string. If the resultant string is to be used as a *data* for POST + operation with the :func:`~urllib.request.urlopen` function, then + it should be encoded to bytes, otherwise it would result in a + :exc:`TypeError`. The resulting string is a series of ``key=value`` pairs separated by ``'&'`` characters, where both *key* and *value* are quoted using the *quote_via* diff -r 4df1eaecb506 -r 6ff71efb3b5b Doc/library/urllib.request.rst --- a/Doc/library/urllib.request.rst Sat Nov 07 03:15:32 2015 +0000 +++ b/Doc/library/urllib.request.rst Sat Nov 07 08:36:34 2015 +0000 @@ -36,13 +36,8 @@ *data* should be a buffer in the standard :mimetype:`application/x-www-form-urlencoded` format. The :func:`urllib.parse.urlencode` function takes a mapping or sequence of - 2-tuples and returns a string in this format. It should be encoded to bytes - before being used as the *data* parameter. The charset parameter in - ``Content-Type`` header may be used to specify the encoding. If charset - parameter is not sent with the Content-Type header, the server following the - HTTP 1.1 recommendation may assume that the data is encoded in ISO-8859-1 - encoding. It is advisable to use charset parameter with encoding used in - ``Content-Type`` header with the :class:`Request`. + 2-tuples and returns an ASCII text string in this format. It should + be encoded to bytes before being used as the *data* parameter. urllib.request module uses HTTP/1.1 and includes ``Connection:close`` header in its HTTP requests. @@ -180,16 +175,9 @@ the only ones that use *data*; the HTTP request will be a POST instead of a GET when the *data* parameter is provided. *data* should be a buffer in the standard :mimetype:`application/x-www-form-urlencoded` format. - The :func:`urllib.parse.urlencode` function takes a mapping or sequence of - 2-tuples and returns a string in this format. It should be encoded to bytes - before being used as the *data* parameter. The charset parameter in - ``Content-Type`` header may be used to specify the encoding. If charset - parameter is not sent with the Content-Type header, the server following the - HTTP 1.1 recommendation may assume that the data is encoded in ISO-8859-1 - encoding. It is advisable to use charset parameter with encoding used in - ``Content-Type`` header with the :class:`Request`. - + 2-tuples and returns an ASCII string in this format. It should be + encoded to bytes before being used as the *data* parameter. *headers* should be a dictionary, and will be treated as if :meth:`add_header` was called with each key and value as arguments. @@ -202,7 +190,7 @@ ``"Python-urllib/2.6"`` (on Python 2.6). An example of using ``Content-Type`` header with *data* argument would be - sending a dictionary like ``{"Content-Type":" application/x-www-form-urlencoded;charset=utf-8"}``. + sending a dictionary like ``{"Content-Type": "application/x-www-form-urlencoded"}``. The final two arguments are only of interest for correct handling of third-party HTTP cookies: @@ -1230,7 +1218,7 @@ opener.open('http://www.example.com/') Also, remember that a few standard headers (:mailheader:`Content-Length`, -:mailheader:`Content-Type` without charset parameter and :mailheader:`Host`) +:mailheader:`Content-Type` and :mailheader:`Host`) are added when the :class:`Request` is passed to :func:`urlopen` (or :meth:`OpenerDirector.open`). @@ -1253,11 +1241,8 @@ >>> import urllib.request >>> import urllib.parse >>> data = urllib.parse.urlencode({'spam': 1, 'eggs': 2, 'bacon': 0}) - >>> data = data.encode('utf-8') - >>> request = urllib.request.Request("http://requestb.in/xrbl82xr") - >>> # adding charset parameter to the Content-Type header. - >>> request.add_header("Content-Type","application/x-www-form-urlencoded;charset=utf-8") - >>> with urllib.request.urlopen(request, data) as f: + >>> data = data.encode('ascii') + >>> with urllib.request.urlopen("http://requestb.in/xrbl82xr", data) as f: ... print(f.read().decode('utf-8')) ... diff -r 4df1eaecb506 -r 6ff71efb3b5b Lib/urllib/request.py --- a/Lib/urllib/request.py Sat Nov 07 03:15:32 2015 +0000 +++ b/Lib/urllib/request.py Sat Nov 07 08:36:34 2015 +0000 @@ -149,13 +149,8 @@ *data* should be a buffer in the standard application/x-www-form-urlencoded format. The urllib.parse.urlencode() function takes a mapping or sequence - of 2-tuples and returns a string in this format. It should be encoded to - bytes before being used as the data parameter. The charset parameter in - Content-Type header may be used to specify the encoding. If charset - parameter is not sent with the Content-Type header, the server following - the HTTP 1.1 recommendation may assume that the data is encoded in - ISO-8859-1 encoding. It is advisable to use charset parameter with encoding - used in Content-Type header with the Request. + of 2-tuples and returns an ASCII text string in this format. It should be + encoded to bytes before being used as the data parameter. urllib.request module uses HTTP/1.1 and includes a "Connection:close" header in its HTTP requests. [View Less]

1 0

Remove “Content-Type: application/x-www-form-urlencoded; charset” advice (issue 25576)
by rdmurray＠bitdance.com Nov. 9, 2015

Nov. 9, 2015

http://bugs.python.org/review/25576/diff/15901/Doc/library/urllib.request.r… File Doc/library/urllib.request.rst (right): http://bugs.python.org/review/25576/diff/15901/Doc/library/urllib.request.r… Doc/library/urllib.request.rst:1245: >>> with urllib.request.urlopen("http://requestb.in/xrbl82xr", data) as f: We lose something from the example no longer showing a use of add_header. Is there any other header we could add that would make sense in context? I don't think it is a big … [View More]

1 0

[issue25064] Adjust tempfile documentation for bytes filename support
by Martin Panter Nov. 7, 2015

Nov. 7, 2015

New submission from Martin Panter: This is a followup to Issue 24230, which added support for bytes filenames to “tempfile” module. Currently I think the documentation is misleading, for example it suggests the default values are prefix="tmp" and suffix="", when they are actually None to avoid forcing a text filename. I suggest this patch to fix the problem. The patch also merges the paragraphs that describe “suffix” and “prefix”, and points out that mktemp() does not support these changes. -… [View More]

2 2

[issue25428] Have `datetime` understand integer arguments for timezones
by leewz Nov. 7, 2015

Nov. 7, 2015

New submission from leewz: Current: If I want to create a datetime object with a particular timezone offset, I have to do this: import datetime mytime = datetime.datetime(2015, 10, 16, 9, 13, 0, tzinfo=datetime.timezone(datetime.timedelta(hours=-7))) Or with imports: from datetime import datetime, timezone, timedelta mytime = datetime(2015, 10, 16, 9, 13, 0, tzinfo=timezone(timedelta(hours=-7))) That's two extra imports and two extra objects created. Requested way: … [View More] mytime = datetime(2015, 10, 16, 9, 13, 0, tzinfo=-7) # mytime.tzinfo == -7 Or if someone doesn't like the `tzinfo` keyword: mytime = datetime(2015, 10, 16, 9, 13, 0, tzhours=-7) # mytime.tzinfo == timezone(timedelta(-7)) For timezones, hours are the normal unit of time. At least, I think about time zones in hours, and I don't know who would think about them in minutes. There are half-hour offsets, so floats make sense to have. Imagine you have about a year of experience dabbling in Python, and you're trying to do a relatively simple task, like reading PDT times and converting them to local time. You would go to the datetime docs, see that you need to pass in a tzinfo object. You look that up, and run into this: """tzinfo is an abstract base class, meaning that this class should not be instantiated directly. You need to derive a concrete subclass, and (at least) supply implementations of the standard tzinfo methods needed by the datetime methods you use.""" Well, great. If you want to convert times, you'll have to subclass an abstract base class, and implement five methods. You'd probably have to read the whole docs for this class, too. (The docs for tzinfo take nine Page Downs for me to scroll past.) If you're not frightened off by the first two sentences, you'll see that there's the concrete subclass `datetime.timezone`. We're two levels down, now. Going there, you'll see that you need to pass in a timedelta object. Three levels. You need to learn about three classes just to specify an hour offset. Timezones are something that many non-programmers understand, and the rules are pretty simple (barring DST, but the library doesn't really deal with it anyway). Ideally, it should be simple to do simple things. PS: There seems to be unnecessary inconsistency with `.astimezone`, `fromtimestamp`, and `now` taking a `tz` kwarg rather than a `tzinfo` kwarg. ---------- assignee: docs@python components: Documentation, Library (Lib) messages: 253111 nosy: docs@python, leewz priority: normal severity: normal status: open title: Have `datetime` understand integer arguments for timezones type: enhancement versions: Python 3.5, Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue25428> _______________________________________ [View Less]

3 3

Python problems on Windows 1o
by Lester Veenstra Nov. 6, 2015

Nov. 6, 2015

Could not IDLE to run under WINDOWS 10 install ENV Path includes ;d:\python27 When I try to invoke Tinker from inside python, I get C:\Users\lbv>python Python 2.7.10 (default, May 23 2015, 09:40:32) [MSC v.1500 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import Tkinter Traceback (most recent call last): File "<stdin>", line 1, in <module> File "d:\python27\lib\lib-tk\Tkinter.py", line 38, … [View More]

1 0