Mailman 3 December 2016 - docs

is (big-endian) ?
by Volunteer Dec. 6, 2016

Dec. 6, 2016

https://docs.python.org/3/library/struct.html 7.1.2.1. Byte Order, Size, and Alignment Native byte order is big-endian or little-endian, depending on the host system. For example, Intel x86 and AMD64 (x86-64) are little-endian; Motorola 68000 and PowerPC G5 are big-endian; ARM and Intel Itanium feature switchable endianness (bi-endian). Use sys.byteorder to check the endianness of your system. endianness (bi-endian) error? is (big-endian) ? .

2 2

Re: [docs] hex() documentation: mention "%x" % int (issue 26506)
by julien+python＠palard.fr Dec. 5, 2016

Dec. 5, 2016

I'm not fan of "If prefix "0b" is desired or not", I'm not a native english but I think it should be changed. http://bugs.python.org/review/26506/diff/16805/Doc/library/functions.rst File Doc/library/functions.rst (right): http://bugs.python.org/review/26506/diff/16805/Doc/library/functions.rst#ne… Doc/library/functions.rst:92: If prefix "0b" is desired or not, you can use either of the following ways. See I'm not a big fan of "is desired or not", why not avoiding it with something like: "When more flexibility is needed, :func:`format` can also format hexadecimal strings:" (If so, please change it on the three different places for consistency). http://bugs.python.org/review/26506/

1 0

Re: [docs] Fixed all the doctest failures in Doc/library/configparser.rst (issue 28860)
by marco.buttu＠gmail.com Dec. 5, 2016

Dec. 5, 2016

http://bugs.python.org/review/28860/diff/19350/Doc/library/configparser.rst File Doc/library/configparser.rst (left): http://bugs.python.org/review/28860/diff/19350/Doc/library/configparser.rst… Doc/library/configparser.rst:73: >>> import configparser On 2016/12/05 13:29:56, berkerpeksag wrote: > On 2016/12/05 13:20:11, marco.buttu wrote: > > On 2016/12/05 12:27:28, berkerpeksag wrote: > > > Can this be removed now? (since we've already import it in testsetup?) > > > > I think it is really important to keep it at the beginning, because the code > we > > show to the reader has to be working code. The user has to import configparser > > in the shell before executing manually the example. The import in the > testsetup > > has just the purpose to avoid the same import in all the examples, when they > > belong to the same session. > > Yes, that's a good point. I didn't notice it was the first example of the > documentation. In any case, the testsetup is not required (we can remove it), because all the doctests are executed in the same session, and configparser is imported from the beginning. So, in a final patch, I will remove it http://bugs.python.org/review/28860/

1 0

Re: [docs] Fixed all the doctest failures in Doc/library/configparser.rst (issue 28860)
by berker.peksag＠gmail.com Dec. 5, 2016

Dec. 5, 2016

http://bugs.python.org/review/28860/diff/19350/Doc/library/configparser.rst File Doc/library/configparser.rst (left): http://bugs.python.org/review/28860/diff/19350/Doc/library/configparser.rst… Doc/library/configparser.rst:73: >>> import configparser On 2016/12/05 13:20:11, marco.buttu wrote: > On 2016/12/05 12:27:28, berkerpeksag wrote: > > Can this be removed now? (since we've already import it in testsetup?) > > I think it is really important to keep it at the beginning, because the code we > show to the reader has to be working code. The user has to import configparser > in the shell before executing manually the example. The import in the testsetup > has just the purpose to avoid the same import in all the examples, when they > belong to the same session. Yes, that's a good point. I didn't notice it was the first example of the documentation. http://bugs.python.org/review/28860/

1 0

Re: [docs] Fixed all the doctest failures in Doc/library/configparser.rst (issue 28860)
by marco.buttu＠gmail.com Dec. 5, 2016

Dec. 5, 2016

Reviewers: berkerpeksag, http://bugs.python.org/review/28860/diff/19350/Doc/library/configparser.rst File Doc/library/configparser.rst (left): http://bugs.python.org/review/28860/diff/19350/Doc/library/configparser.rst… Doc/library/configparser.rst:73: >>> import configparser On 2016/12/05 12:27:28, berkerpeksag wrote: > Can this be removed now? (since we've already import it in testsetup?) I think it is really important to keep it at the beginning, because the code we show to the reader has to be working code. The user has to import configparser in the shell before executing manually the example. The import in the testsetup has just the purpose to avoid the same import in all the examples, when they belong to the same session. http://bugs.python.org/review/28860/diff/19350/Doc/library/configparser.rst File Doc/library/configparser.rst (right): http://bugs.python.org/review/28860/diff/19350/Doc/library/configparser.rst… Doc/library/configparser.rst:476: >>> sorted(parser.sections()) On 2016/12/05 12:27:28, berkerpeksag wrote: > I'd skip this one like you did in your first patch. > > As a reader, I find using sorted() here less readable and more confusing. > > +1 for using sorted() in the iteration examples (but I'd skip them too since > they may have already tested in Lib/test/test_configparser.py) I agree with you, it is less readable and more confusing. Sometimes we need a treadoff, and when the API is enough stable that the test result, in all likelihood, will not change in future Python versions, we can take the risk to skip the test. Please review this at http://bugs.python.org/review/28860/ Affected files: Doc/library/configparser.rst diff -r 16350c1f81a1 Doc/library/configparser.rst --- a/Doc/library/configparser.rst Sun Dec 04 10:22:36 2016 +0200 +++ b/Doc/library/configparser.rst Sun Dec 04 10:12:10 2016 +0100 @@ -68,6 +68,10 @@ :mod:`configparser` classes can read and write such files. Let's start by creating the above configuration file programmatically. +.. testsetup:: + + import configparser + .. doctest:: >>> import configparser @@ -116,13 +120,13 @@ 'no' >>> topsecret['Port'] '50022' - >>> for key in config['bitbucket.org']: print(key) - ... + >>> for key in sorted(config['bitbucket.org']): + ... print(key) + compression + compressionlevel + forwardx11 + serveraliveinterval user - compressionlevel - serveraliveinterval - compression - forwardx11 >>> config['bitbucket.org']['ForwardX11'] 'yes' @@ -469,10 +473,10 @@ ... 'bar': 'y', ... 'baz': 'z'} ... }) - >>> parser.sections() - ['section3', 'section2', 'section1'] - >>> [option for option in parser['section3']] - ['baz', 'foo', 'bar'] + >>> sorted(parser.sections()) + ['section1', 'section2', 'section3'] + >>> sorted(option for option in parser['section3']) + ['bar', 'baz', 'foo'] In these operations you need to use an ordered dictionary as well: @@ -514,8 +518,6 @@ .. doctest:: - >>> import configparser - >>> sample_config = """ ... [mysqld] ... user = mysql @@ -571,7 +573,9 @@ values with characters used as comment prefixes. When in doubt, avoid setting *inline_comment_prefixes*. In any circumstances, the only way of storing comment prefix characters at the beginning of a line in multiline - values is to interpolate the prefix, for example:: + values is to interpolate the prefix, for example: + + .. doctest:: >>> from configparser import ConfigParser, ExtendedInterpolation >>> parser = ConfigParser(interpolation=ExtendedInterpolation()) @@ -597,11 +601,11 @@ ... line #3 ... """) >>> print(parser['hashes']['shebang']) - + <BLANKLINE> #!/usr/bin/env python # -*- coding: utf-8 -*- >>> print(parser['hashes']['extensions']) - + <BLANKLINE> enabled_extension another_extension yet_another_extension @@ -755,6 +759,7 @@ .. doctest:: + >>> import re >>> config = """ ... [Section 1] ... option = value @@ -762,11 +767,11 @@ ... [ Section 2 ] ... another = val ... """ - >>> typical = ConfigParser() + >>> typical = configparser.ConfigParser() >>> typical.read_string(config) >>> typical.sections() ['Section 1', ' Section 2 '] - >>> custom = ConfigParser() + >>> custom = configparser.ConfigParser() >>> custom.SECTCRE = re.compile(r"\[ *(?P<header>[^]]+?) *\]") >>> custom.read_string(config) >>> custom.sections()

1 0

Fixed all the doctest failures in Doc/library/configparser.rst (issue 28860)
by berker.peksag＠gmail.com Dec. 5, 2016

Dec. 5, 2016

http://bugs.python.org/review/28860/diff/19350/Doc/library/configparser.rst File Doc/library/configparser.rst (left): http://bugs.python.org/review/28860/diff/19350/Doc/library/configparser.rst… Doc/library/configparser.rst:73: >>> import configparser Can this be removed now? (since we've already import it in testsetup?) http://bugs.python.org/review/28860/diff/19350/Doc/library/configparser.rst… Doc/library/configparser.rst:576: >>> from configparser import ConfigParser, ExtendedInterpolation Perhaps we can change this example to use configparser.foo format and remove this line too? http://bugs.python.org/review/28860/diff/19350/Doc/library/configparser.rst File Doc/library/configparser.rst (right): http://bugs.python.org/review/28860/diff/19350/Doc/library/configparser.rst… Doc/library/configparser.rst:476: >>> sorted(parser.sections()) I'd skip this one like you did in your first patch. As a reader, I find using sorted() here less readable and more confusing. +1 for using sorted() in the iteration examples (but I'd skip them too since they may have already tested in Lib/test/test_configparser.py) http://bugs.python.org/review/28860/

1 0

Python.org tutorial multiple-inheritance chapter bug
by Антон Онуфриев Dec. 5, 2016

Dec. 5, 2016

https://docs.python.org/3.6/tutorial/classes.html#multiple-inheritance Hello. There is a phrase about searching in base classes in text on link above: Thus, if an attribute is not found in DerivedClassName, it is searched for in Base1, then (recursively) in the base classes of Base1, and if it was not found there, it was searched for in Base2, and so on. I think it's a bug in a documentation and newer version of Python search methods in other way, using c3-linearization method. -- Onufriev Anton

1 0

Just open a py file I have saved
by Dave R Dec. 5, 2016

Dec. 5, 2016

I am using windows ten. I invoke python by putting myself in the Python35-32 folder and running python,exe. Why cant I just open and save valid py files ? I can click on a py file that is valid python commands and it runs, But how can I open and save such files from within the interpreter ? Thank you. Dave Richter

1 0

[issue27050] Demote run() below the high level APIs in subprocess docs
by Nick Coghlan Dec. 4, 2016

Dec. 4, 2016

Nick Coghlan added the comment: I've switched to using Vinay Sajip's "sarge" for my own subprocess invocation needs, which uses a similar all-in-one "run" API (albeit quite a different approach to capturing output). Accordingly, I don't think there's anything useful to be done specifically in the context of this issue - any energy that might be spent here would likely be spent more constructively on things like making the pipe encoding easier to configure, or reducing the risk of deadlocks due to OS-level buffer size limits. ---------- resolution: -> not a bug status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue27050> _______________________________________

1 0

[issue28868] Python advertising BeOpen.com domain
by rm Dec. 4, 2016

Dec. 4, 2016

New submission from rm: There is BeOpen attribution in __builtins__() call, that may confuse users and generate some traffic to unrelated domain. For example: >>> import smtplib >>> smtplib.__builtins__ <...> Copyright (c) 2000 BeOpen.com. All Rights Reserved. <...> but beopen.com resolves to domain hosting stub page. May be this string should be changed to just BeOpen, or removed altogether. ---------- assignee: docs@python components: Documentation messages: 282361 nosy: cvs-src, docs@python priority: normal severity: normal status: open title: Python advertising BeOpen.com domain versions: Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28868> _______________________________________

3 2