Mailman 3 March 2007 - Python-Dev

Distutils and -framework on MacOSX
by Greg Ewing April 4, 2007

April 4, 2007

Has anyone found a way of persuading distutils to pass MacOSX -framework options properly when linking? Using extra_link_args doesn't work, because they need to be at the beginning of the command line to work properly, but extra_link_args gets put at the end. And extra_compile_args is only used when compiling, not linking. -- Greg

2 4

About SSL tests
by Facundo Batista April 4, 2007

April 4, 2007

There's this bug (#451607) about the needing of tests for socket SSL... Last interesting update in the tracker is five years ago, and since a lot of work has been done in test_socket_ssl.py (Brett, Neal, Tim, George Brandl). Do you think is useful to leave this bug opened? Regards, -- . Facundo . Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/

10 25

proposed which.py replacement
by Shane Geiger April 2, 2007

April 2, 2007

Trent Mick has a module called which.py that might make a nice platform-independent replacement for python2.5/Tools/scripts/which.py. http://www.trentm.com/projects/which/ Why which.py? |which.py| is a small GNU-which replacement. It has the following features: * it is portable (Windows, Linux, Mac OS X, Un*x); * it understands PATHEXT and "App Paths" registration on Windows (i.e. it will find everything that |start| does from the command shell); * it can print all matches on the PATH; * it can note "near misses" on the PATH (e.g. files that match but may not, say, have execute permissions); and * it can be used as a Python module. I also would be happy to have this be a replacement for the |which.py| in the Python CVS tree at |dist/src/Tools/scripts/which.py| which is Unix-specific and not usable as a module; and perhaps for inclusion in the stdlib. -- Shane Geiger IT Director National Council on Economic Education sgeiger(a)ncee.net | 402-438-8958 | http://www.ncee.net Leading the Campaign for Economic and Financial Literacy

6 10

BaseException pickle issue
by Eric Huss April 1, 2007

April 1, 2007

Some subclasses of Exception are no longer pickleable in Python 2.5. An example: class A(Exception): def __init__(self, foo): self.foo = foo The key problem here is if you do not somehow set self.args to the correct arguments (via Exception.__init__ or setting self.args directly), you will get a TypeError when you try to unpickle it: TypeError: __init__() takes exactly 2 arguments (1 given) I do not think this is unusual. I found a few examples in Python's standard library that have this problem: subprocess.CalledProcessError HTMLParser.HTMLParseError httplib.UnknownProtocol, httplib.IncompleteRead, httplib.BadStatusLine optparse.OptParseError pickle._Stop and on and on... Does anyone have any thoughts about this? Is it a bug? I can imagine one could argue that exceptions should call the base __init__ method to properly set args, but there are so many exceptions out there that do not do this that it would be very difficult to track them all down. I removed the __reduce__ and __setstate__ methods from BaseException and everything seems to just work. Pickling/unpickling works for all protocols whether or not you set self.args. Is this an appropriate solution? I'm not sure what the motivation for having these methods is. -Eric

2 2

Get 2.5 changes in now, branch will be frozen soon
by Neal Norwitz April 1, 2007

April 1, 2007

This is a reminder that the 2.5 branch will be frozen early next week. If there are changes you want to get into 2.5.1, they should be checked in within a few days. Be conservative! There will be a 2.5.2, it's better to wait than to have to make a new release for one rushed feature. If you don't believe, just wait until Anthony shows up at your doorstep. :-) n

7 8

p2p vpn in python?
by Shane Geiger March 30, 2007

March 30, 2007

Is anyone in the Python world considering writing a P2P VPN application in Python (a la Hamachi)? -- Shane Geiger IT Director National Council on Economic Education sgeiger(a)ncee.net | 402-438-8958 | http://www.ncee.net Leading the Campaign for Economic and Financial Literacy

3 2

Italic text in the manual
by BJörn Lindqvist March 29, 2007

March 29, 2007

(This might be a silly question..) In the dev stdlib reference there are lots of pages in which all text is in italics. Such as all chapters after chapter 18. Is it supposed to be that way? It looks quite ugly. -- mvh Björn

6 6

Should TemporaryFile() return a wrapper like NamedTemporaryFile()?
by Raghuram Devarakonda March 29, 2007

March 29, 2007

Hi, I am looking into the issue http://python.org/sf/1615275 (suggested by Neal) and added a comment there. I would appreciate it if some one can check it out and comment on it. Basically, I am wondering if TemporaryFile() should return a wrapper instance (with "file" member) just like NamedTemporaryFile(). It shouldn't effect any existing code (unless I am missing something) but should help in cross-platform code. Thanks, Raghu.

1 1

Possible bugs in test_struct
by Collin Winter March 29, 2007

March 29, 2007

While converting test_struct to use unittest, I came across these two issues: 1) r51119 by Bob Ippolito added a test case for "SF bug 1530559: struct.pack raises TypeError where it used to convert." (Handy diff at http://svn.python.org/view/python/trunk/Lib/test/test_struct.py?rev=51119&r…). As far as I can tell, this test doesn't work, thanks to the lines check_float_coerce = with_warning_restore(deprecated_err) def test_1530559(): for endian in ('', '>', '<'): for fmt in ('B', 'H', 'I', 'L', 'b', 'h', 'i', 'l'): check_float_coerce(endian + fmt, 1.0) check_float_coerce(endian + fmt, 1.5) The problem is that the calls to check_float_coerce() attempt to call the string produced by "endian + fmt", so a TypeError will always be raised. Fixing the test to do what was actually intended causes a TestFailed error to be raised with the message "did not raise error for float coerce". I'm confused as to why this is a test failure, when it seems like "rais[ing an] error for float coerce" is exactly what we're trying to avoid. Anyone know what's going on here? 2) test_705836() features the code big = (1 << 25) - 1 big = math.ldexp(big, 127 - 24) try: packed = struct.pack(">f", big) except OverflowError: pass else: TestFailed("expected OverflowError") Actually raising the TestFailed exception (as opposed to just instantiating it) causes a test failure. Is this a bug in struct or a bad test? Thanks, Collin Winter

1 0

A simplified extended buffer PEP
by Jim Jewett March 29, 2007

March 29, 2007

Greg Ewing wrote: > Carl Banks wrote: > > /* don't define releasebuffer or lockbuffer */ > > /* only objects that manage buffers themselves would define these */ > That's an advantage, but it's a pretty small one ... > the releaser field makes the protocol asymmetrical > and thus harder to reason about. Instead of "releaser", how about an "owner" field, that points to a PyObject? PyObject_GetBuffer will create a new reference to owner, and unlock/release is just a DECREF on that same object. (Or does redirecting the DECREF target like this look too magical?) If a buffer exporter want to keep things simple, it can just set "owner" to self. If it has fancier needs (such as mutating the buffer without mutating the view), then it can create a manager to do whatever it wants, and set that as the owner. Note that the PyBufferProcs structure isn't needed any more -- from a consumer/requestor's perspective, the unlock/release is just DECREFing the owner. Looking at http://projects.scipy.org/scipy/numpy/browser/trunk/numpy/doc/pep_buffer.txt (Other than utility functions like PyObject_SizeFromFormat,) I think the entire protocol can then collapse to the bufferinfo struct and either // might set an error and return NULL struct bufferinfo *PyObject_GetBuffer(PyObject *obj, int flags) or // Replace the *view elements with the actual buffers metadata // (return = 0) ==> success // (return > 0) ==> modified (perhaps rejecting the RO argument)? // (return < 0) ==> failure int PyObject_GetBuffer(PyObject *obj, struct bufferinfo *view) -jJ

1 0