Mailman 3 July 2012 - Python-Dev

EuroPython 2012 Language Summit Is In JEOPARDY *gasp*
by Larry Hastings July 4, 2012

July 4, 2012

So far I've had exactly four reservations for the Language Summit at EuroPython 2012. One of them is Guido--but he's threatening to skip it if we don't get more people and just go to the sprints. Also, honestly I have next-to-nothing on the docket. At this point we've just hit feature freeze for Python 3.3--or at least that's what people tell me. In general, anyone who wanted to get a language change in have already either just succeeded or just failed. So after a flurry of activity I … [View More]

1 0

Re: [Python-Dev] cpython: Issue #15210: If _frozen_importlib is not found in sys.modules by
by Antoine Pitrou July 2, 2012

July 2, 2012

On Mon, 2 Jul 2012 20:53:15 +0200 (CEST) brett.cannon <python-checkins(a)python.org> wrote: > http://hg.python.org/cpython/rev/818db871d29a > changeset: 77916:818db871d29a > user: Brett Cannon <brett(a)python.org> > date: Mon Jul 02 14:53:10 2012 -0400 > summary: > Issue #15210: If _frozen_importlib is not found in sys.modules by > importlib.__init__, then catch the KeyError raised, not ImportError. There's a test failure here: http://buildbot.python.org/all/builders/AMD64%20Fedora%20without%20threads%… Regards Antoine.

1 0

New stable buildbots
by Antoine Pitrou July 2, 2012

July 2, 2012

Hello, I have decided to add two new buildslaves to the stable buildbots fleet: - Łukasz Langa's AMD64 OS Lion buildbot (using clang as compiler) - Jeremy Kloth's AMD64 Windows7 buildbot (our first 64-bit Windows buildbot!) They bring the number of stable buildbots to twelve: 4 Windows, 5 Linux and 3 other Unices: http://buildbot.python.org/all/waterfall?category=3.x.stable Regards Antoine.

2 2

Failed issue tracker submission
by Python tracker July 2, 2012

July 2, 2012

There was a problem with the message you sent: This issue can't be closed until issue <a href="http://bugs.python.org/issue15031">15031</a> is closed. Mail Gateway Help ================= Incoming messages are examined for multiple parts: . In a multipart/mixed message or part, each subpart is extracted and examined. The text/plain subparts are assembled to form the textual body of the message, to be stored in the file associated with a "msg" class node. Any parts of … [View More]other types are each stored in separate files and given "file" class nodes that are linked to the "msg" node. . In a multipart/alternative message or part, we look for a text/plain subpart and ignore the other parts. . A message/rfc822 is treated similar tomultipart/mixed (except for special handling of the first text part) if unpack_rfc822 is set in the mailgw config section. Summary ------- The "summary" property on message nodes is taken from the first non-quoting section in the message body. The message body is divided into sections by blank lines. Sections where the second and all subsequent lines begin with a ">" or "|" character are considered "quoting sections". The first line of the first non-quoting section becomes the summary of the message. Addresses --------- All of the addresses in the To: and Cc: headers of the incoming message are looked up among the user nodes, and the corresponding users are placed in the "recipients" property on the new "msg" node. The address in the From: header similarly determines the "author" property of the new "msg" node. The default handling for addresses that don't have corresponding users is to create new users with no passwords and a username equal to the address. (The web interface does not permit logins for users with no passwords.) If we prefer to reject mail from outside sources, we can simply register an auditor on the "user" class that prevents the creation of user nodes with no passwords. Actions ------- The subject line of the incoming message is examined to determine whether the message is an attempt to create a new item or to discuss an existing item. A designator enclosed in square brackets is sought as the first thing on the subject line (after skipping any "Fwd:" or "Re:" prefixes). If an item designator (class name and id number) is found there, the newly created "msg" node is added to the "messages" property for that item, and any new "file" nodes are added to the "files" property for the item. If just an item class name is found there, we attempt to create a new item of that class with its "messages" property initialized to contain the new "msg" node and its "files" property initialized to contain any new "file" nodes. Triggers -------- Both cases may trigger detectors (in the first case we are calling the set() method to add the message to the item's spool; in the second case we are calling the create() method to create a new node). If an auditor raises an exception, the original message is bounced back to the sender with the explanatory message given in the exception. $Id: mailgw.py,v 1.196 2008-07-23 03:04:44 richard Exp $ Return-Path: <python-dev(a)python.org> X-Original-To: report(a)bugs.python.org Delivered-To: roundup+tracker(a)psf.upfronthosting.co.za Received: from mail.python.org (mail.python.org [82.94.164.166]) by psf.upfronthosting.co.za (Postfix) with ESMTPS id 5E7D11CC7C for <report(a)bugs.python.org>; Mon, 2 Jul 2012 20:36:31 +0200 (CEST) Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3WQxxp54vszPJ6 for <report(a)bugs.python.org>; Mon, 2 Jul 2012 20:36:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901; t=1341254190; bh=bcoPtckr6VOn/nnWeOnKJxf0E8057TGiXziLdKxmDAU=; h=MIME-Version:Content-Type:Content-Transfer-Encoding:From:To: Subject:Message-Id:Date; b=LeXZP20cZnfbA2FHjnPNH2KEX5ZCGryZdBwT5XwAqbn2PrdQCxB0OJ766NdEkuI5N RlaB95Vz83qouHfh8sVxO8welo9E4UpoXVEEvwFt5/XYUtDG3eoVp6ufKpWCxut1Sj PDwgNWINBY5UPYtDB92G1S7YTLttEiQ/jt2a/vaE= Received: from localhost (HELO mail.python.org) (127.0.0.1) by albatross.python.org with SMTP; 02 Jul 2012 20:36:30 +0200 Received: from virt-7yvsjn.psf.osuosl.org (virt-7yvsjn.psf.osuosl.org [140.211.10.72]) by mail.python.org (Postfix) with ESMTP for <report(a)bugs.python.org>; Mon, 2 Jul 2012 20:36:30 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 From: python-dev(a)python.org To: report(a)bugs.python.org Subject: [issue15030] [status=closed; resolution=fixed; stage=committed/rejected] Message-Id: <3WQxxp54vszPJ6(a)mail.python.org> Date: Mon, 2 Jul 2012 20:36:30 +0200 (CEST) TmV3IGNoYW5nZXNldCBiNzQ2M2VjMTk4MGMgYnkgQnJldHQgQ2Fubm9uIGluIGJyYW5jaCAnZGVm YXVsdCc6CkNsb3NlcyAjMTUwMzA6IE1ha2UgaW1wb3J0bGliLmFiYy5QeVB5Y0xvYWRlciByZXNw ZWN0IHRoZSBuZXcgLnB5YwpodHRwOi8vaGcucHl0aG9uLm9yZy9jcHl0aG9uL3Jldi9iNzQ2M2Vj MTk4MGMK [View Less]

1 0

Re: [Python-Dev] Announcing the python-static-type-checking google group
by Paul Boddie July 1, 2012

July 1, 2012

Stefan Behnel wrote: > Paul Boddie, 01.07.2012 02:22: > > Is there any reason why the compiler-sig mailing list wasn't chosen as a > > venue > > Even I didn't know that this list even existed. And looking at the archives > now, it's hard to see any relevant discussion in all the spam it received > until it apparently died away in (almost) silence a couple of years ago. Yes, although the mailing lists for special interest groups are advertised on python.org, there is … [View More]no longer the focus on steering discussion to those lists. And I see that the compiler SIG is "retired", as is the related types SIG: http://www.python.org/community/sigs/retired/ I seem to remember various procedures about SIGs and their retirement, but I don't really recall much discussion of such things recently. Still, the compiler SIG matches the scope of the Google group pretty well: http://www.python.org/community/sigs/retired/compiler-sig/ There's even a link to discussion of some tools you may be familiar with. > > It's obviously your choice where you host discussions and who you invite, > > and I know that the special interest group mailing lists aren't exactly > > well advertised these days > > True, but many (most?) of them are simply not very well frequented, which > reduces the interest in joining them even further. Both SIG mailing lists > that I read only receive a mail every so many months, often enough without > any reply. And almost all of these mails deal with questions that would > better be discussed on python-list to leverage the substantially higher > number of eyeballs there. Special interest group lists were always meant to be used as focused channels of communication where people are actively trying to get stuff done. The unfortunate thing is that they aren't as well known as they were. Another unfortunate thing is that getting stuff done of mutual benefit is frequently something that takes second place to whatever other motivations and goals people have, for whatever reason, good or bad. Thus, traffic drops away as people either do other things entirely or instead promote any related work in other channels instead. > I think that's the basic problem: as long as more experts are lurking on > python-list than on the dedicated SIG-ML, it's better not to use the SIG-ML > for discussions but to go to python-list (or maybe python-ideas or > python-dev) straight away. I think we really have to sort out what python-dev is for, because currently there's a tendency to target the list when any kind of "expert" discussion is required, but there are a number of people who would rather see only CPython-related discussion here. Another matter is that static analysis of Python is a topic that frequently hits the end of the road when one cannot, by definition, analyze Python in its most dynamic form, and when people refuse to accept that such analysis has anything to do with Python in its most pure, undiluted (and most contrived) form. But as I wrote, I still intend to follow the newly created group and see what people have to say. Paul [View Less]

1 0

hg.python.org migrated
by Antoine Pitrou July 1, 2012

July 1, 2012

Hello, hg.python.org has just been migrated to a new (virtual) machine hosted by OSU OSL (*). Until the domain name fully propagates, you won't be able to push or pull from the repositories using the ssh protocol. If you notice other issues, don't hesitate to mention them. (*) http://osuosl.org/ Regards Antoine.

1 0

Re: [Python-Dev] Announcing the python-static-type-checking google group
by Paul Boddie July 1, 2012

July 1, 2012

Edward K. Ream wrote: > Hello all, > > GvR has asked me to announce the python-static-type-checking google > group http://groups.google.com/group/python-static-type-checking to > python-dev. > > Consider it announced. Anyone from python-dev who likes may become a > member. Is there any reason why the compiler-sig mailing list wasn't chosen as a venue for such discussions? I know it has "compiler" in the title, but the mandate overlaps significantly with what you … [View More]

3 2

cross-compiling patches
by Antoine Pitrou July 1, 2012

July 1, 2012

Hello, I think these patches are premature (they break compilation on OS X, and they break ctypes configure on my Linux box). Furthermore, they were committed post-beta, which means they should probably have waited for after the 3.3 release. So I propose for these commits to be reverted. (to be clear, I'm talking about all configure / Makefile / setup.py / libffi changes since and including http://hg.python.org/cpython/rev/e6e99d449bdc876fa57111e7e534c44ecbc3bcbd ) Regards Antoine.

4 4

Re: [Python-Dev] cpython: Add syntax highlighter tool
by Georg Brandl July 1, 2012

July 1, 2012

On 01.07.2012 01:58, raymond.hettinger wrote: > http://hg.python.org/cpython/rev/da4dd603030b > changeset: 77899:da4dd603030b > user: Raymond Hettinger <python(a)rcn.com> > date: Sat Jun 30 16:58:06 2012 -0700 > summary: > Add syntax highlighter tool > > files: > Tools/scripts/pycolorize.py | 109 ++++++++++++++++++++++++ > 1 files changed, 109 insertions(+), 0 deletions(-) Uh, this looks quite a lot like a new feature... Since it's … [View More]

1 0