Mailman 3 April 2001 - Python-Dev

2.1c1: 2nd test_asynchat fails on Solaris 8
by Mark Favas April 15, 2001

April 15, 2001

SunOS asafoetida 5.8, gcc 2.95.2 "make test" fails on running test_asynchat.py for the second time. The traceback is: Exception in thread Thread-1: Traceback (most recent call last): File "/export/home/mark/src/python/CVS/python/dist/src/Lib/threading.py", line 378, in __bootstrap self.run() File "Lib/test/test_asynchat.py", line 12, in run sock.bind((HOST, PORT)) error: (125, 'Address already in use') Traceback (most recent call last): File "Lib/test/test_asynchat.py", line 56, in ? main() File "Lib/test/test_asynchat.py", line 51, in main c = echo_client() File "Lib/test/test_asynchat.py", line 32, in __init__ self.connect((HOST, PORT)) File "/export/home/mark/src/python/CVS/python/dist/src/Lib/asyncore.py", line 308, in connect raise socket.error, why socket.error: (146, 'Connection refused') Looks like Solaris takes a while to shut sockets down? (This is not a slow box, btw.) Or is there an option to not have the socket linger? Also, test_sunaudiodev fails, since setup.py tests only whether the platform is a Sun, not whether there is a /dev/audio as well. Servers don't have a /dev/audio. This is clearly a minor nit - I did log a bug against this some time ago. -- Mark Favas - m.favas(a)per.dem.csiro.au CSIRO, Private Bag No 5, Wembley, Western Australia 6913, AUSTRALIA

3 5

[development doc updates]
by fdrake＠beowolf.digicool.com April 14, 2001

April 14, 2001

The development version of the documentation has been updated: http://python.sourceforge.net/devel-docs/ Final Python 2.1 documentation.

1 0

2.1c1: test_zipfile fails on FreeBSD
by Mark Favas April 14, 2001

April 14, 2001

FreeBSD 4.2-20010225-STABLE, gcc 2.95.2 ./python Lib/test/test_zipfile.py Traceback (most recent call last): File "Lib/test/test_zipfile.py", line 35, in ? zipTest(file, zipfile.ZIP_STORED, writtenData) File "Lib/test/test_zipfile.py", line 18, in zipTest zip.close() File "/home/mark/src/python/CVS/python/dist/src/Lib/zipfile.py", line 471, in close self.fp.flush() IOError: [Errno 9] Bad file descriptor Looks like FreeBSD objects to doing a flush() on a file opened for reading. The self.fp.flush() call should probably be part of the preceding if-block relating to files opened in "a" or "w' mode. -- Mark Favas - m.favas(a)per.dem.csiro.au CSIRO, Private Bag No 5, Wembley, Western Australia 6913, AUSTRALIA

4 4

2.1c1 OK with Numeric -- and a testing question
by Paul F. Dubois April 14, 2001

April 14, 2001

I built Numeric with 2.1c1 (on Windows) and it passes all our tests. I intend to convert the Numeric tests to use PyUnit at some point. Is there a recommended example? I converted the MA test suite by just reading the PyUnit web page and I have the feeling I'm missing something. I made it work but it wasn't any nicer than my existing test when I got done. (ANYTHING is more elegant than the existing Numeric test).

1 0

Re: [Python-Dev] Cygwin Python 2.1c1 test_threadedtempfile problem
by Jason Tishler April 14, 2001

April 14, 2001

Tim, On Sat, Apr 14, 2001 at 06:01:07AM -0400, Tim Peters wrote: > I bet this fresh SF bug report explains it: > > http://sourceforge.net/tracker/?func=detail&atid=105470&aid=416089&group_id… Bingo! See the following: $ ./python Python 2.1c1 (#1, Apr 13 2001, 21:47:33) [GCC 2.95.3-2 (cygwin special)] on cygwin_nt-4.01 Type "copyright", "credits" or "license" for more information. >>> import threading Traceback (most recent call last): File "<stdin>", line 1, in ? File "/home/jt/src/Python-2.1c1/Lib/threading.py", line 5, in ? import thread ImportError: No module named thread >>> import threading >>> > Instead they deliver a, umm, bogus module object <wink>. I've > never liked this behavior -- but probably can't change it for 2.1 final. It > won't be the first time we've needed to worm around it in the test suite > either ... Oh well, there is always 2.2... Thanks, Jason -- Jason Tishler Director, Software Engineering Phone: +1 (732) 264-8770 x235 Dot Hill Systems Corp. Fax: +1 (732) 264-8798 82 Bethany Road, Suite 7 Email: Jason.Tishler(a)dothill.com Hazlet, NJ 07730 USA WWW: http://www.dothill.com

1 0

Cygwin Python 2.1c1 test_threadedtempfile problem
by Jason Tishler April 14, 2001

April 14, 2001

I configured as follows: configure --with-threads=no When I run the regression tests I get the following: test test_threadedtempfile crashed -- exceptions.AttributeError: 'threading' module has no attribute 'Event' Should this test only be run if Python is built with thread support? Thanks, Jason -- Jason Tishler Director, Software Engineering Phone: +1 (732) 264-8770 x235 Dot Hill Systems Corp. Fax: +1 (732) 264-8798 82 Bethany Road, Suite 7 Email: Jason.Tishler(a)dothill.com Hazlet, NJ 07730 USA WWW: http://www.dothill.com

3 3

2.1c1: "make test" core dumps on SGI Irix
by Mark Favas April 14, 2001

April 14, 2001

IRIX64 dodo 6.5 07201607 IP35, MIPSpro Compilers: Version 7.30 "make test" core dumps with no output from any test completed. Running them one-by-one reveals that the (first?) core dump is in test___all__.py. python Lib/test/test___all__.py Bus error (core dumped) dbx where gives: (chopped) > 0 float_mul(0x100ce7dc, 0x103523d8, 0x8, 0x100b5d70, 0x10050000, 0x103523d8, 0x100b5d70, 0x100b5ce8) ["/tmp_mnt/home/solo/mark/python/Python-2.1c1/Objects/floatobject.c":382, 0x1004f098] 1 binary_op1(0x100ce7dc, 0x103523d8, 0x0, 0x100b5d70, 0x10050000, 0x103523d8, 0x100b5d70, 0x100b5ce8) ["/tmp_mnt/home/solo/mark/python/Python-2.1c1/Objects/abstract.c":337, 0x1003bfec] 2 binary_op(0x100ce7dc, 0x103523d8, 0x8, 0x0, 0x10050000, 0x103523d8, 0x100b5d70, 0x100b5ce8) ["/tmp_mnt/home/solo/mark/python/Python-2.1c1/Objects/abstract.c":373, 0x1003c200] 3 PyNumber_Multiply(0x100ce7dc, 0x103523d8, 0x8, 0x100b5d70, 0x10050000, 0x103523d8, 0x100b5d70, 0x100b5ce8) ["/tmp_mnt/home/solo/mark/python/Python-2.1c1/Objects/abstract.c":544, 0x1003c934] 4 eval_code2(0x101bea78, 0x0, 0x0, 0x0, 0x103ffad7, 0x0, 0x0, 0x0) ["/tmp_mnt/home/solo/mark/python/Python-2.1c1/Python/ceval.c":945, 0x10035cb4] 5 PyEval_EvalCode(0x100ce7dc, 0x103523d8, 0x8, 0x100b5d70, 0x10050000, 0x103523d8, 0x100b5d70, 0x100b5ce8) ["/tmp_mnt/home/solo/mark/python/Python-2.1c1/Python/ceval.c":341, 0x10032818] 6 PyImport_ExecCodeModuleEx(0x7fff1168, 0x0, 0x0, 0x100b5d70, 0x10050000, 0x103523d8, 0x0, 0x100b5ce8) ["/tmp_mnt/home/solo/mark/python/Python-2.1c1/Python/import.c":490, 0x1000d904] 7 load_source_module(0x0, 0x7fff0840, 0x0, 0x100b5d70, 0x10050000, 0x103523d8, 0x100b5d70, 0x100b5ce8) ["/tmp_mnt/home/solo/mark/python/Python-2.1c1/Python/import.c":754, 0x1000e0f0] More (n if no)? -- Mark Favas - m.favas(a)per.dem.csiro.au CSIRO, Private Bag No 5, Wembley, Western Australia 6913, AUSTRALIA

2 2

Complex detection
by Paul F. Dubois April 13, 2001

April 13, 2001

My understanding is that Python can be built without complex numbers to satisfy the needs of the Python-on-a-wristwatch crowd. Is there a run-time way to tell? For example, using an imaginary literal causes an error? If so, what kind? I'm finishing the reference implementation for PEP 242 and want to allow for this possibility.

3 2

compileall.py and make install
by Jeremy Hylton April 13, 2001

April 13, 2001

There are two related problems that I'd like to fix for the release candidate. One is that compileall.py basically ignores compiler errors. It's clear that the code intends to return with a non-zero exit status if there are compilation errors, but it doesn't do that currently. If I fix just this problem, make install will start to fail because there are six files in the test directory that contain intentional SyntaxErrors; in one case, it's necessary that the SyntaxError be raised through import. I'd like to fix compileall.py and add an optional argument that tells it to skip files that match a regular expression. Then I'll rename all the offending files so that they are named badsyntax_XXX and fix the Makefile so that it installs them but does not compile them. This is going to cause two problems for developers. First, you'll need to manually delete the files with the old names from the install lib directory. (I'll rename nocaret.py to badsyntax_nocaret.py, but, if you've already done an install, you'll also have a nocaret.py in the lib directory.) The compileall script also traverses into site-packages. If you have compilation errors in code that you've installed into site-packages, then make install will fail. I'm not sure what to do about this. During development, at least, it is probably helpful for make install to walk into site-packages and fail if the new version of Python breaks existing code. On the other hand, it could be a big pain that you can't install Python just because you previously installed a buggy Python library. Of course, you could just remove the broken code. I think it's a net gain to make these changes. Is anyone more concerned that me about the possible breakage? Jeremy

2 4

[development doc updates]
by fdrake＠beowolf.digicool.com April 13, 2001

April 13, 2001

The development version of the documentation has been updated: http://python.sourceforge.net/devel-docs/ Final documentation for Python 2.1c1.

1 0