Mailman 3 November 2007 - Python-Dev

test_doctest failing
by Brett Cannon Nov. 25, 2007

Nov. 25, 2007

Looks like Skip's r59137 fix for working with tracing has led to test_doctest to be broken on 2.5 and the trunk (at least according to the buildbots). Can someone either revert the commit or fix it? I would normally do it myself but US Thanksgiving has me tied up to not do too much beyond bitching about the amount of buildbot emails I have been getting. =) -Brett

4 6

Re: [Python-Dev] Should we do away with unbound methods in Py3k?
by Phillip J. Eby Nov. 24, 2007

Nov. 24, 2007

At 09:56 AM 11/24/2007 -0800, Guido van Rossum wrote: >Also, there was discussion of this before: >http://mail.python.org/pipermail/python-dev/2005-January/050625.html >-- why didn't we decide to do it then? http://mail.python.org/pipermail/python-dev/2005-January/051236.html There were also a few protests of use cases that could not be worked around (e.g. pickling methods), and a few people pointed out that the type checking actually *is* useful when using explicit base calls (… [View More]

1 0

Backquote deprecation warning
by Christian Heimes Nov. 24, 2007

Nov. 24, 2007

Hello! I'm having a bit of a trouble getting the deprecation warning for backquotes `repr` right. Neither the ast_for_* functions in Python/ast.c nor the node structures have access to the filename. Should the node structure gain an additional field to drag the filename around? Or can we simply life with the fact that the user won't get a filename in the deprecation warning? Christian

4 4

ssl module integration with asyncore
by Giampaolo Rodola' Nov. 23, 2007

Nov. 23, 2007

Hi there, since ssl module is still in development I thought it would have been better asking such question here instead of on comp.lang.python. I'm interested in using the ssl module with asyncore but since there's no real documentation about it yet I've been not able to write something useful with it. Currently I'm trying to add the SSL support to an asyncore-based FTP server I wrote. I tried to write some code by watching the ssl-related test-suite scripts with no luck since there are no … [View More]

1 0

Summary of Tracker Issues
by Tracker Nov. 23, 2007

Nov. 23, 2007

ACTIVITY SUMMARY (11/16/07 - 11/23/07) Tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 1321 open (+20) / 11654 closed (+20) / 12975 total (+40) Open issues with patches: 413 Average duration of open issues: 697 days. Median duration of open issues: 825 days. Open Issues Breakdown open 1314 (+19) pending 7 ( +1) Issues Created Or Reopened (41) _______________________________ … [View More]

1 0

1324 bugs in the tracker
by Christian Heimes Nov. 23, 2007

Nov. 23, 2007

Dear fellow Python developers! The Python bug tracker contains more than 1,300 bugs and it's growing. And growing ... and growing. I'm picking a bug once in a while or tossing some invalid bugs away but it's a helpless cause. The bugs are augmenting with anybody stopping them. Well, I'm exaggerating a bit but you probably get my point. The core developers can't keep up with new bugs and check old bugs at the same time. The resources are already stretched thin. But Brett gave me an idea how we … [View More]

3 5

Re: [Python-Dev] Should we do away with unbound methods in Py3k?
by Phillip J. Eby Nov. 23, 2007

Nov. 23, 2007

At 08:19 PM 11/22/2007 -0800, Guido van Rossum wrote: >It looks like we're in agreement to drop unbound methods and have a >reasonable set or arguments around it (e.g. keep staticmethod, no >changes to methods of builtin types, etc.). Do we need a PEP? It's >essentially a 2-line change in funcobject.c (func_descr_get()) -- plus >fixing up half a dozen or so unittests that specifically seem to test >the behavior of unbound methods. Since the only meaningful difference between … [View More]an unbound method and a function is the availability of the im_class attribute, I Googled 'im_class ext:py' to see what's using it. There were 314 hits uses in published code, and I skimmed the first 60 or 70 of those. Of the ones I looked at, relatively few actually do anything with unbound methods specifically. Most are just custom pickling or persistence for methods, or method replacements like a "weakref method" that doesn't keep a strong reference to im_self. However, a few uses relevant to unbound methods turned up, however. Some documentation tools, an AOP library, an xreload()-like module reloader from Enthought, plus one usage in the stdlib. There were also a few modules where it was difficult to tell if unbound methods were actually important. While for most of the documentation tools it was probably not relevant, there were some (like a method deprecation utility) that looked like they would lose functionality by not being able to get the im_class of an object. The stdlib usage is in the unittest module: the test loading machinery needs to know the class of an unbound method so it knows what TestCase subclass to instantiate, when loading a single test by name. This could probably be worked around by making the routine keep track of the object from which the target object was retrieved. This is far from a comprehensive survey; 'UnboundMethodType ext:py' turns up 102 more hits, including another testing tool that uses unbound methods in a different way. There are also usage patterns that can't easily be searched for. For example, code that wants to be able to distinguish static methods and instance methods at the class level. Most of these use cases could probably be worked around, with sufficient effort. Many will probably have bigger problems porting to 3.0 than the absence of unbound methods. And I don't personally have a horse in this race, as my own code is surprisingly free of im_class use. Actually, given how many places my code is peppered with '.im_func' calls to *unwrap* unbound methods and reuse them in other classes, I probably lean more towards getting rid of them. :) [View Less]

1 0

PCbuild9 for the trunk
by Christian Heimes Nov. 22, 2007

Nov. 22, 2007

Just for your information: I've back-ported the PCbuild9 directory from py3k to the trunk. You now can build Python 2.6 and 3.0 with the new Visual Studio 2008. As far as I've heard from other it works with the free Express Edition. MSDN subscribers with the Standard or Professional version can also create PGO builds with the new directory. Preliminary tests are showing that PGO builds are roughly 10% faster than standard builds. Have fun! Christian

2 2

Tracker summary emails
by Paul Moore Nov. 22, 2007

Nov. 22, 2007

Is it only me who thinks that the current daily summaries are a bit frequent? Would it be possible to reduce the frequency to, say, once a week? I can set up a filter to simply ditch the things, but I thought I'd check what other people's views are before I did. Paul.

4 6

A crash during interpreter cleanup when using PyGILState APIs
by Ronald Oussoren Nov. 22, 2007

Nov. 22, 2007

An extension module I use makes extensive use of the PyGILState API's in callback functions for C APIs. Some of the functions that use the PyGILState APIs are used in the tp_dealloc of methods. This seems cause problems when objects are cleaned up during interpreter shutdown: when an object is deallocated during PyInterpreterState_Clear I get a hard crash because the GILState machinery has been shut down at that time :-( The bug report for this: http://bugs.python.org/issue1402 … [View More]

1 0