Mailman 3 March 2002 - Python-Dev

(python-dev��) ��Żī�޶� & ��ĳ�� .(ȫ^��)
by ��Ÿ March 27, 2002

March 27, 2002

1 0

OT: Looking for a couple panelists for a meeting in late May
by Skip Montanaro March 27, 2002

March 27, 2002

(private replies to skip(a)pobox.com, please) Please forgive the off-topic post. I am helping to organize (read: sort of got roped into) the May Technology Executives Roundtable here in Evanston, Illinois. The May 28th TER meeting is scheduled to have a panel discussion on "Profiting from Open Source Software". I have lined up one panelist, Rob Page, CEO and co-founder of Zope, but a couple other possibilities have fallen through. I am looking for two or three more people to be on the panel. They need not be from the Python community. Meetings typically run from about 6pm to 9pm, begin with a half hour of networking, followed by brief presentations from the panelists, the usual rubber chicken dinner, then Q&A from the floor. Attendance is usually in the 50-person range, split pretty evenly between techies and business types. If you or someone you know with substantial experience building a business based on open source software (whatever definition of that loaded phrase you care to use) are or will be in the Chicago area on or about the 28th, please let me know or pass this note along. For general info about TER, visit their website at <http://www.ter1.com/>. Thanks, Skip

1 0

In-place multiply and new style classes
by Todd Miller March 27, 2002

March 27, 2002

Hi, I'm Todd Miller and I work at the Space Telescope Science Institute on Numarray. Numarray is STSCI's stab at improving Numeric. This is my first post here. Today one of the guys in my branch noticed that Numarray's in-place multiply was raising this bizarre exception: --> a = ones ((5,), Float32) --> a array([1., 1., 1., 1., 1.], type=Float32) --> a *= 62. Traceback (innermost last): File "<console>", line 1, in ? TypeError: can't multiply sequence to non-int I looked into this for a couple hours and discovered the following: class test1(object): """A new-style class""" def __init__(self): pass def __imul__(self, other): print "no luck here!" >>> t1 = test1() >>> t1 *= 62. Traceback (most recent call last): File "<stdin>", line 1, in ? TypeError: can't multiply sequence to non-int Todd -- Todd Miller jmiller(a)stsci.edu STSCI / SSG (410) 338 4576

2 2

RELEASED: Python 2.2.1c2
by Michael Hudson March 27, 2002

March 27, 2002

We've released a second release candidate for the next bugfix release of Python, 2.2.1. There haven't been many changes since 2.2.1c1, just a few fixes. Note for AIX users: there are still problems with AIX in this release, and there has not been time to repair them without fear of breaking platforms that currently work. Hopefully by the time of the release of 2.2.1 final we will be able to provide a recipe that allows AIX users to build and run Python. Get the scoop (and the files) here: http://www.python.org/2.2.1/ In order to make 2.2.1 a solid release, please help by + Building the release, and running the test suite on your platform. + Running *your* extension modules' and applications' test suites against this release. + Reporting any problems to the bug tracker at sf: http://sourceforge.net/bugs/?group_id=5470 This being a bugfix release, there are no exciting new features -- we just fixed a lot of bugs. For a moderately complete list, please see: http://sourceforge.net/project/shownotes.php?release_id=81373 Feel free to email me the output of "make test", but please check that you are not duplicating effort by reading this page first: http://starship.python.net/crew/mwh/221c2-reports.txt 2.2.1 final will follow "soon". Cheers, The Python development team.

3 2

PEP 282 comments
by Jeremy Hylton March 27, 2002

March 27, 2002

I think the log4j levels are sufficient. zLOG has more levels, but it's hard to figure out what to use them for :-). zLOG does have a nice feature for passing an exception info to a log call. I'd like to see this as a standard feature, e.g. logger.info("A normal exception occurred", exc_info=sys.exc_info()) The idea is the any of the log calls could also include a formatted traceback in the log. (I suppose this means that the Handlers need a pluggable way to format exceptions.) This is useful for all log levels. In a long running server, you may get exceptions that are unexpected but no so important that you're going to fail or bring the server down. What's the current status of this PEP? I like the general outline of stuff, but it feels a little fuzzy. That is, it seems to present a high-level description and a bunch of options. I'd like to see the concrete APIs for all of the objects. I'd also love to get at least a prototype implementation. It would be need to replace the zLOG in Zope3 with a new logging implementation that follows the PEP. Jeremy

18 71

[development doc updates]
by Fred L. Drake March 26, 2002

March 26, 2002

The development version of the documentation has been updated: http://python.sourceforge.net/devel-docs/ Minor update; shows how the "What's New" document is linked in.

1 0

Mandrake 8.2 anyone?
by barry＠zope.com March 26, 2002

March 26, 2002

Has anybody else run the test suite for Py2.3cvs under Mandrake 8.2? I'm seeing some very weird problems, but my komputer karma is running a bit sour today, so I wanted some confirmation. Maybe I should move to Montana soon. Specifically, the first time I ran it earlier today (fresh cvs update, make distclean, configure, make test), the test suite hung in test_linuxaudiodev. Running that test manually also produced a hang. These weren't killable, even with kill -9, C-\, or C-z, and couldn't be gdb attached to. So I rebooted and tried again. This time the tests don't hang but they do fail: test test_linuxaudiodev crashed -- linuxaudiodev.error: (0, 'Error') Hmm. gonna-be-a-mental-toss-flycoon-ly y'rs, -Barry

3 6

Re: [Python-Dev] RE: [Python-checkins] CVS: python/dist/src/Lib pickle.py,1.57,1.58
by Michael Hudson March 26, 2002

March 26, 2002

Guido van Rossum <guido(a)python.org> writes: > > > Bugfix candidate (but I think it's too late for 2.2.1). > > > > Because ...? The 2.2.1c2 Windows installer won't get built today, > > and the tarball won't get cut at least until Michael has another cut > > at the NEWS file. So it's not too late to put it into 2.2.1 if you > > feel confident about this change. > > Because Michael said "no more checkins". He's also gone to bed, I've gotten up again now. > I trust, and I don't feel like overriding him without talking to him > first. Maybe he'll be happy to add this to the branch in the > morning. It looks harmless enough, it's in. Skip wrote: > There's always a third possibility: 2.2.1c3, but I would assume > that's mostly Michael's call. Will all due repect, NFW[0]. Cheers, M. [0] If it helps to work this acronym out, the middle word is rude. -- ARTHUR: Why are there three of you? LINTILLAS: Why is there only one of you? ARTHUR: Er... Could I have notice of that question? -- The Hitch-Hikers Guide to the Galaxy, Episode 11

2 1

iterkeys, itervalues, iteritems for dict-proxies
by Walter Dörwald March 26, 2002

March 26, 2002

iterkeys(), itervalues() and iteritems() are missing from dict-proxy objects. Was this done on purpose or was it an oversight? Should these missing methods be added (and the "XXX" docstrings be fixed along the way)? Bye, Walter Dörwald -- Walter Dörwald · LivingLogic AG, Bayreuth/Germany · www.livinglogic.de

3 8

Re: [Python-Dev] 2.2.1c1 platform reports.
by Michael Hudson March 26, 2002

March 26, 2002

Andrew MacIntyre <andymac(a)bullseye.apana.org.au> writes: > On 25 Mar 2002, Michael Hudson wrote: > > > Andrew MacIntyre <andymac(a)bullseye.apana.org.au> writes: > > {...} > > > > Sorry, I've not had time to look at this for the OS/2-EMX build; maybe > > > tonight. > > > > I thought OS/2-EMX was only going to be supported in 2.3? I'm > > certainly not going to port all those checkins you made to the -maint > > branch. > > I wasn't expecting them to be backported, and I don't expect the release > sourceball to contain the OS/2 EMX changes until 2.3 either. Good. > I do however plan a binary release of 2.2.1 from my local CVS. If there > were any problems apparently not related specifically to my OS/2 patches, > I'd let you know. It's getting kind of late for these to make any difference... > In particular the test_math run you requested feedback about (as a > datapoint, not something you could/should resolve). Again, good (the me not having to do anythign part :). > As I've had system problems, and am not sure whether I've got my local > vendor-branch 2.2 CVS tree straightened out after importing 2.2C1, I > haven't had anything to report :-( Well, OK, it would be nice to have, but don't push yourself about it... Cheers, M. -- Monte Carlo sampling is no way to understand code. -- Gordon McMillan, comp.lang.python

1 0