[Python-Dev] Re: Can't build Zope on Windows w/ 2.4.1c1

Tres Seaver tseaver at zope.com
Thu Mar 10 21:02:31 CET 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anthony Baxter wrote:
| It works on Linux, with Zope 2.7.4. Just as a note to others (I've
mentioned
| this to Tim already) if you set an environment variable DISTUTILS_DEBUG
| before running a setup.py, you get very verbose information about
what's going
| on, and, more importantly, full tracebacks rather than terse error
messages.
|
| error: No such file or directory
|
| looks like a distutils error message.

Unit tests for Zope 2.7.4's 'zdaemon' package, which passed under Python
2.4, now fail under 2.4.1c1:

$ uname -a
Linux secretariat 2.6.8.1-5-686 #1 Sat Feb 12 00:50:37 UTC 2005 i686 \
GNU/Linux
$ ../Python-2.4/python test.py -v zdaemon
Running unit tests at level 1
Running unit tests from
/home/tseaver/projects/Zope-CVS/Zope-2.7.4/lib/python
/home/tseaver/projects/Zope-CVS/Python-2.4/Lib/whrandom.py:38:
DeprecationWarning: the whrandom module is deprecated; please use the
random module
~  DeprecationWarning)
............................
- ----------------------------------------------------------------------
Ran 28 tests in 2.278s

OK
$ ../Python-2.4.1c1/python test.py -v zdaemon
Running unit tests at level 1
Running unit tests from
/home/tseaver/projects/Zope-CVS/Zope-2.7.4/lib/python
/home/tseaver/projects/Zope-CVS/Python-2.4.1c1/Lib/whrandom.py:38:
DeprecationWarning: the whrandom module is deprecated; please use the
random module
~  DeprecationWarning)
...................Traceback (most recent call last):
~  File "test.py", line 918, in ?
~    process_args()
~  File "test.py", line 908, in process_args
~    bad = main(module_filter, test_filter, libdir)
~  File "test.py", line 698, in main
~    runner(files, test_filter, debug)
~  File "test.py", line 599, in runner
~    r = runner.run(suite)
~  File "test.py", line 366, in run
~    return unittest.TextTestRunner.run(self, test)
~  File "/home/tseaver/projects/Zope-CVS/Python-2.4.1c1/Lib/unittest.py",
line 696, in run
~    test(result)
~  File "/home/tseaver/projects/Zope-CVS/Python-2.4.1c1/Lib/unittest.py",
line 428, in __call__
~    return self.run(*args, **kwds)
~  File "/home/tseaver/projects/Zope-CVS/Python-2.4.1c1/Lib/unittest.py",
line 424, in run
~    test(result)
~  File "/home/tseaver/projects/Zope-CVS/Python-2.4.1c1/Lib/unittest.py",
line 428, in __call__
~    return self.run(*args, **kwds)
~  File "/home/tseaver/projects/Zope-CVS/Python-2.4.1c1/Lib/unittest.py",
line 424, in run
~    test(result)
~  File "/home/tseaver/projects/Zope-CVS/Python-2.4.1c1/Lib/unittest.py",
line 428, in __call__
~    return self.run(*args, **kwds)
~  File "/home/tseaver/projects/Zope-CVS/Python-2.4.1c1/Lib/unittest.py",
line 424, in run
~    test(result)
~  File "/home/tseaver/projects/Zope-CVS/Python-2.4.1c1/Lib/unittest.py",
line 281, in __call__
~    return self.run(*args, **kwds)
~  File
"/home/tseaver/projects/Zope-CVS/Zope-2.7.4/lib/python/zdaemon/tests/testzdrun.py",
line 97, in run
~    zdctl.main(["-s", self.zdsock] + args)
AttributeError: 'ZDaemonTests' object has no attribute 'zdsock'


By staring at the code of the failing test, it looks like the MRO of the
testcase class has changed:  it declares a 'run' method, which is
supposed to run the external process, which clashes with the 'run'
method of unittest.TestCase.  I don't know what change in the 2.4 ->
2.4.1c1 update would have mucked with the MRO (if a MRO issue is involved).


Tres.
- --
===============================================================
Tres Seaver                                tseaver at zope.com
Zope Corporation      "Zope Dealers"       http://www.zope.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCMKfXGqWXf00rNCgRAn8sAJ40b9THGi81tRJItjl1kTo+7kV86QCffBKu
+7CnIOgjvNQ3jlFl4PRDJ9c=
=oyGX
-----END PGP SIGNATURE-----



More information about the Python-Dev mailing list