Mailman 3 January 2015 - Python-Dev

PEP 484
by Mario Figueiredo Jan. 24, 2015

Jan. 24, 2015

Please don't clutter executable code. We need to read it without growing an headache. Much better is: def myfunction(arg1, arg2): """ Normal docstring... @hint: (str, int) -> bool """ return True While I agree type hinting, for the purposes of static analysis, has no place in __doc__, I think that we could live with that. Otherwise: def myfunction(arg1, arg2): """ Normal docstring... """ "@hint: (str, int) -> bool" return True

1 0

Summary of Python tracker Issues
by Python tracker Jan. 24, 2015

Jan. 24, 2015

ACTIVITY SUMMARY (2015-01-16 - 2015-01-23) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 4760 (+24) closed 30307 (+30) total 35067 (+54) Open issues with patches: 2228 Issues opened (38) ================== #23095: [Windows] asyncio: race condition when cancelling a _WaitHandl http://bugs.python.org/issue23095 reopened by haypo #23252: Add … [View More]

1 0

PEP 448 (almost finished!) — Question regarding test_ast
by Neil Girdhar Jan. 23, 2015

Jan. 23, 2015

My question first: test_ast is mostly generated code, but I can't find where it is being generated. I am pretty sure I know how to fix most of the introduced problems. Who is generating test_ast?? Update: So far, I've done the following: Updated the patch to 3.5 Fixed the grammar to accept final commas in argument lists always, and to work with the already implemented code. Fixed the ast to accept what it needs to accept and reject according to the limitation laid down by Guido. Fixed the … [View More]

3 8

Re: [Python-Dev] [Python-checkins] cpython (3.4): Remove the unimplemented but ignored without='-E' parameters being passed to
by Gregory P. Smith Jan. 23, 2015

Jan. 23, 2015

I misinterpreted the side effect this code was triggering. It turns out that any kwarg would have the desired effect as a side effect (as seen in dummyvar='' being passed later in this file for the same purpose). I'm looking at refactoring various uses of -E that interfere with running the test suite in an environment where you need PYTHONHOME set. I will revert this change or otherwise do the equivalent of reinstating its behavior in a followup check-in as appropriate. -gregory.p.smith On … [View More]Thu Jan 22 2015 at 10:05:56 PM gregory.p.smith < python-checkins(a)python.org> wrote: > https://hg.python.org/cpython/rev/7b833bd1f509 > changeset: 94249:7b833bd1f509 > branch: 3.4 > parent: 94247:7f3ac2ce24ed > user: Gregory P. Smith <greg(a)krypto.org> > date: Thu Jan 22 22:04:16 2015 -0800 > summary: > Remove the unimplemented but ignored without='-E' parameters being > passed to > script_helper.assert_python_failure(). No such feature has ever existed, > thus it doesn't do what the comment claims. (It does add a 'without' > variable to the environment of the child process but that was not intended) > > files: > Lib/test/test_cmd_line.py | 6 ++---- > 1 files changed, 2 insertions(+), 4 deletions(-) > > > diff --git a/Lib/test/test_cmd_line.py b/Lib/test/test_cmd_line.py > --- a/Lib/test/test_cmd_line.py > +++ b/Lib/test/test_cmd_line.py > @@ -426,13 +426,11 @@ > self.assertIn(b'Unknown option: -z', err) > self.assertEqual(err.splitlines().count(b'Unknown option: -z'), > 1) > self.assertEqual(b'', out) > - # Add "without='-E'" to prevent _assert_python to append -E > - # to env_vars and change the output of stderr > - rc, out, err = assert_python_failure('-z', without='-E') > + rc, out, err = assert_python_failure('-z') > self.assertIn(b'Unknown option: -z', err) > self.assertEqual(err.splitlines().count(b'Unknown option: -z'), > 1) > self.assertEqual(b'', out) > - rc, out, err = assert_python_failure('-a', '-z', without='-E') > + rc, out, err = assert_python_failure('-a', '-z') > self.assertIn(b'Unknown option: -a', err) > # only the first unknown option is reported > self.assertNotIn(b'Unknown option: -z', err) > > -- > Repository URL: https://hg.python.org/cpython > _______________________________________________ > Python-checkins mailing list > Python-checkins(a)python.org > https://mail.python.org/mailman/listinfo/python-checkins > [View Less]

1 0

Why does STORE_MAP not take a parameter?
by Neil Girdhar Jan. 22, 2015

Jan. 22, 2015

Building argument lists and dicts in python entails the following opcode pattern: 1 0 BUILD_MAP 3 3 LOAD_CONST 0 (2) 6 LOAD_CONST 1 (1) 9 STORE_MAP 10 LOAD_CONST 2 (4) 13 LOAD_CONST 3 (3) 16 STORE_MAP 17 LOAD_CONST 4 (6) 20 LOAD_CONST 5 (5) 23 STORE_MAP Building … [View More]

3 2

incorrect docstring for sys.int_info.sizeof_digit?
by Pfeiffer, Phillip E., IV Jan. 21, 2015

Jan. 21, 2015

Apologies if this has already been reported; I couldn't find a readily searchable archive for this mailing list (and apologies if I've just missed it). Issue: the docstring for sys.int_info_.sizeof_digit appears to be amiss; see below. ------ Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Windows\system32>python Python 3.4.2 (v3.4.2:ab2c023a9432, Oct 6 2014, 22:16:31) [MSC v.1600 64 bit (AMD64)] on win32 Type "help", "copyright", "… [View More]

3 2

sorry for the last e-mail
by Pfeiffer, Phillip E., IV Jan. 21, 2015

Jan. 21, 2015

Apologies for being stupid. I've been away from Python for awhile, and just realized that I'm simply seeing the docstring for int when I check out sys.int_info.whatever, where .whatever is an int-valued attribute. While it would be nice to have a clearer description of the sys.int_info's attributes in the sys.int_info docstring, that's a different kettle of fish. Again, apologies. -- Phil =================== Phil Pfeiffer/ East TN State U. | Kindness in thought leads to … [View More]

1 0

Re: [Python-Dev] [Python-ideas] What's going on with PEP 448 - Additional Unpacking Generalizations ?
by Guido van Rossum Jan. 21, 2015

Jan. 21, 2015

Thanks very much for your work! I am CC'ing python-dev to see if there are any last calls for PEP 448. Assuming no material objection appear to the new syntax and semantics, I can approve the PEP later this week. To get it committed, you need one of the active committers to give you a code review (waiting for me would mean waiting forever). Maybe Antoine, Benjamin or Victor? On Tue, Jan 20, 2015 at 9:39 AM, Neil Girdhar <mistersheik(a)gmail.com> wrote: > I believe I have finally … [View More]finished the work on the patch for PEP 448 ( > http://bugs.python.org/issue2292). How do we get the PEP approved? What > else would we need to check it into Python? > > Best, > > Neil > > On Tue, Jan 20, 2015 at 12:03 PM, Guido van Rossum <guido(a)python.org> > wrote: > >> OK. I don't like arg unpackings after keyword args, for the same reason >> plain positional args aren't allowed after keyword args, but I guess I >> didn't pay attention when it was introduced, so we're stuck with it now, >> it's not the end of the world, and at least the definition is clear >> (collect all positional args first, then handle keyword args). >> >> On Tue, Jan 20, 2015 at 8:51 AM, Neil Girdhar <mistersheik(a)gmail.com> >> wrote: >> >>> >>> >>> Okay, so: positional arguments neither follow keyword arguments nor >>> keyword argument unpackings; iterable argument unpackings never follow >>> keyword argument unpackings. >>> >>> >>> >>> On Tue, Jan 20, 2015 at 11:47 AM, Joshua Landau <joshua(a)landau.ws> >>> wrote: >>> >>>> On 20 January 2015 at 16:38, Guido van Rossum <guido(a)python.org> wrote: >>>> > The PEP hasn't been accepted yet AFAIK... I'm generally okay with >>>> allowing >>>> > multiple *x things (except in an *unpack* position of course) but I >>>> still >>>> > don't think we should be mixing positional and keyword args. So, no >>>> f(a, >>>> > b=2, c), nor f(a, b=2, *c). >>>> > >>>> >>>> f(a, b=2, *c) is currently legal as both a call and as a definition: >>>> >>>> a, *c = 1, 2, 3 >>>> >>>> def f(*args, **kwargs): >>>> print(args, kwargs) >>>> >>>> f(a, b=2, *c) >>>> #>>> (1, 2, 3) {'b': 2} >>>> >>>> def f(a, b=2, *c): >>>> print(a, b, c) >>>> >>>> f(1, 2, 3) >>>> #>>> 1 2 (3,) >>>> >>>> So I imagine that's staying (or, at least, this PEP isn't removing >>>> it). I don't think anyone is (yet) arguing for f(a, b=2, c). >>>> _______________________________________________ >>>> Python-ideas mailing list >>>> Python-ideas(a)python.org >>>> https://mail.python.org/mailman/listinfo/python-ideas >>>> Code of Conduct: http://python.org/psf/codeofconduct/ >>>> >>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "python-ideas" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/python-ideas/J99EFY1D1nI/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> python-ideas+unsubscribe(a)googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> _______________________________________________ >>> Python-ideas mailing list >>> Python-ideas(a)python.org >>> https://mail.python.org/mailman/listinfo/python-ideas >>> Code of Conduct: http://python.org/psf/codeofconduct/ >>> >> >> >> >> -- >> --Guido van Rossum (python.org/~guido) >> > > -- --Guido van Rossum (python.org/~guido) [View Less]

1 0

bytes & bytearray
by Ethan Furman Jan. 20, 2015

Jan. 20, 2015

I was checking the documentation [1] to see where to put the new information about bytes and bytearray %-formatting, and noticed that /every/ operation that could modify a bytearray object in place (e.g. center, capitalize, strip, etc.) instead returns a new copy. The section just prior to that [2] does say, "As bytearray objects are mutable, they support the mutable sequence operations ...". So it seems that when bytearray is treated as ascii data a new bytearry is returned, and when … [View More]

7 10

Possible "REMOTE HOST IDENTIFICATION HAS CHANGED!" Error.
by Donald Stufft Jan. 20, 2015

Jan. 20, 2015

Just a heads up that people might see a "REMOTE HOST IDENTIFICATION HAS CHANGED!" error when connecting to hg.python.org's SSH (or any other PSF machine). The reason for this is that previously we allowed RSA, ECDSA, and ED25519 host keys. However ECDSA relies on having an unbiased random number generator on every connection and any bias in the random numbers can leak the private key. Since these are running on VMs where we don't know for sure what the quality is of the random numbers I've … [View More]

1 0