Mailman 3 June 2015 - Python-Dev

Summary of Python tracker Issues
by Python tracker June 5, 2015

June 5, 2015

ACTIVITY SUMMARY (2015-05-29 - 2015-06-05) 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 4853 ( +9) closed 31295 (+54) total 36148 (+63) Open issues with patches: 2225 Issues opened (30) ================== #23239: SSL match_hostname does not accept IP Address http://bugs.python.org/issue23239 reopened by christian.heimes #24325: Speedup types.… [View More]

1 0

Unable to build regex module against Python 3.5 32-bit
by MRAB June 5, 2015

June 5, 2015

As the subject says, I've been unable to build the regex module against Python 3.5b1 for 32-bit. MingGW says: skipping incompatible .../libpython35.a when searching for -lpython35 It builds without a problem against Python 3.5 for 64-bit. Any ideas? Should I just wait until beta 2?

6 18

Mingw help
by Steve Dower June 5, 2015

June 5, 2015

If you have an interest in linking to the Windows builds of Python 2.7 and 3.5+ using mingw, please visit http://bugs.python.org/issue24385 Unless someone can provide me with the One True Way to generate a lib that will work for everyone, I'm going to replace the lib file with instructions on how to generate it with your own tools. I've done enough guessing and need someone who actually uses mingw to step up and help out. Thanks, Steve

2 1

Re: [Python-Dev] zipimport
by Rose Ames June 4, 2015

June 4, 2015

On 06/03/2015 08:56 AM, Antoine Pitrou wrote: > Le 03/06/2015 14:34, Rose Ames a écrit : >> >> >> On 06/03/2015 04:59 AM, Antoine Pitrou wrote: >>> On Tue, 02 Jun 2015 21:20:10 +0000 >>> Brett Cannon <brett(a)python.org> wrote: >>>> >>>> I vaguely remember people suggesting writing the minimal zip reading code >>>> in C but I can't remember why since we have I/O access in importlib through >>>> _io and … [View More]

2 1

Fwd: zipimport
by Rose Ames June 3, 2015

June 3, 2015

At pycon I talked with a few people about bugs.python.org/issue19699. The consensus seemed to be that zipimport wants a lot of work, possibly a rewrite. I'll have some time to work on this over the next couple of months, but I want to be working on the right thing. Could the people who were involved in that conversation remind me of their concerns with zipimport? What exactly would the goal of a rewrite be? Thanks, Rose

4 5

Avoiding reference leaks in heap types with custom tp_dealloc
by Petr Viktorin June 2, 2015

June 2, 2015

Hello, The new test_importlib.extension.test_loader is currently leaking references, (issue24268). There is a simple hack to stop this, but I'm inclined to not apply quick hacks and rather dig into the root cause. (It's a test module, the refleaks are relatively harmless.) The tests are based directly on the "xxlimited" example, xxlimited.Xxo, which exhibits the same bug -- it's just not tested. It's is caused by a combination of a few factors, but I'm not sure what's a bug and what's just … [View More]

3 7

Re: [Python-Dev] cpython (2.7): Issue #24357: Change host in socket.getaddrinfo example to one that
by Serhiy Storchaka June 2, 2015

June 2, 2015

On 02.06.15 04:58, ned.deily wrote: > https://hg.python.org/cpython/rev/30da21d2fa4f > changeset: 96458:30da21d2fa4f > branch: 2.7 > parent: 96454:5e8fa1b13516 > user: Ned Deily <nad(a)acm.org> > date: Mon Jun 01 18:45:49 2015 -0700 > summary: > Issue #24357: Change host in socket.getaddrinfo example to one that > does support IPv6 and IPv4; www.python.org currently does not. > > files: > Doc/library/socket.rst | 8 ++++--… [View More]

2 1

RM for 3.6?
by Serhiy Storchaka June 2, 2015

June 2, 2015

Isn't it a time to assign release manager for 3.6-3.7?

8 8

Re: [Python-Dev] [python-committers] Ned Deily is release manager for Python 3.6
by Larry Hastings June 1, 2015

June 1, 2015

On 06/01/2015 11:09 AM, Barry Warsaw wrote: > Please welcome Ned Deily as RM for Python 3.6. > > https://www.python.org/dev/peps/pep-0494/ We're in good hands. For two versions now Benjamin and Ned have been quietly cleaning up my mistakes after (nearly) every release. My guess is, Ned won't bother making the mistakes in the first place! //arry/

1 0

Python 3 migration status update across some key subcommunities (was Re: 2.7 is here until 2020, please don't call it a waste.)
by Nick Coghlan June 1, 2015

June 1, 2015

On 31 May 2015 at 19:07, Ludovic Gasc <gmludo(a)gmail.com> wrote: > About Python 3 migration, I think that one of our best control stick is > newcomers, and by extension, Python trainers/teachers. > If newcomers learn first Python 3, when they will start to work > professionally, they should help to rationalize the Python 3 migration > inside existing dev teams, especially because they don't have an interest > conflict based on the fact that they haven't written plenty … [View More]of code with > Python 2. > 2020 is around the corner, 5 years shouldn't be enough to change the > community mind, I don't know. The education community started switching a while back - if you watch Carrie-Anne Philbin's PyCon UK 2014 keynote, one of her requests for the broader Python community was for everyone else to just catch up already in order to reduce student's confusion (she phrased it more politely than that, though). Educators need to tweak examples and exercises to account for a version switch, but that's substantially easier than migrating hundreds of thousands or even millions of lines of production code. And yes, if you learn Python 3 first, subsequently encountering Python 2's quirks and cruft is likely to encourage folks that know both versions of the language to start advocating for a version upgrade :) After accounting for the "Wow, the existing Python 2 install base is even larger than we realised" factour, the migration is actually in a pretty good place overall these days. The "enterprise" crowd really are likely to be the only ones that might need the full remaining 5 years of migration time (and they may potentially have even more time, if they're relying on a commercial redistributor). Web frameworks have allowed Python 3 development for a while now, and with Django switching their tutorial to Python 3 by default, Django downloads via pip show one of the highest proportions of Python 3 adoption on PyPI. www.python.org itself is now a production Python 3 Django web service, and the next generation of pypi.python.org will be a Pyramid application that's also running on Python 3. The dedicated async/await syntax in 3.5 represents a decent carrot to encourage migration for anyone currently using yield (or yield from) based coroutines, since the distinct syntax not only allows for easier local reasoning about whether something is an iterator or a coroutine, it also provides a much improved user experience for asynchronous iterators and context managers (including finally handling the "asynchronous database transaction as a context manager" case, which previous versions of Python couldn't really do at all). The matrix multiplication operator is similarly a major improvement for the science and data analysis part of the Python community. In terms of reducing *barriers* to adoption, after inviting them to speak at the 2014 language summit, we spent a fair bit of time with the Twisted and Mercurial folks over the past year or so working through "What's still missing from Python 3 for your use cases?", as Python 3.4 was still missing some features for binary data manipulation where we'd been a bit too ruthless in pruning back the binary side of things when deciding what counted as text-only features, and what was applicable to binary data as well. So 3.5 brings back binary interpolation, adds a hex() method to bytes, and adds binary data support directly to a couple of standard library modules (tempfile, difflib). If I understand the situation correctly, the work Guido et al have been doing on PEP 484 and type hinting standardisation is also aimed at reducing barriers to Python 3 adoption, by making it possible to develop better migration tools that are more semantically aware than the existing syntax focused tools. The type hinting actually acts as a carrot as well, since it's a feature that mainly shows its value when attempting to scale a *team* to larger sizes (as it lets you delegate more of the code review process to an automated tool, letting the human reviewers spend more time focusing on higher level semantic concerns). Finally, both Debian/Ubuntu and Fedora are well advanced in their efforts to replace Python 2 with Python 3 in their respective default images (but keeping Py2 available in their package repos). That work is close to finished now (myself, Slavek Kabrda, Barry Warsaw, and Matthias Klose had some good opportunities to discuss that at PyCon), although there are still some significant rough edges to figure out (such as coming up with a coherent cross-platform story for what we're going to do with the Python symlink), as well as a few more key projects to either migrate entirely, or at least finish porting to the source compatible subset of Python 2 & 3 (e.g. Samba). Cheers, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia [View Less]

6 5