[Zope-Checkins] SVN: Zope/trunk/ - Collector #1233: ported ZOPE_CONFIG patch from Zope 2.7 to Zope 2.8

Tim Peters tim.peters at gmail.com
Wed Apr 27 23:16:47 EDT 2005


[Andreas Jung]
> Log message for revision 30205:
>  - Collector #1233: ported ZOPE_CONFIG patch from Zope 2.7 to Zope 2.8
>
> Changed:
>  U   Zope/trunk/doc/CHANGES.txt
>  U   Zope/trunk/lib/python/Zope2/Startup/options.py
>  U   Zope/trunk/lib/python/Zope2/__init__.py

test.py doesn't work at all anymore on Zope trunk, and I suspect this
checkin is the cause (if I revert this checkin on my local box,
test.py works fine again).

The overnight test runners showed one failure mode, which seems to
occur if test.py isn't passed any arguments:

C:\Code\Zope>\python23\python.exe test.py
Running unit tests from C:\Code\Zope\lib\python
Traceback (most recent call last):
  File "test.py", line 917, in ?
    process_args()
  File "test.py", line 907, in process_args
    bad = main(module_filter, test_filter, libdir)
  File "test.py", line 697, in main
    runner(files, test_filter, debug)
  File "test.py", line 591, in runner
    s = get_suite(file, runner.result)
  File "test.py", line 507, in get_suite
    mod = package_import(modname)
  File "test.py", line 481, in package_import
    mod = __import__(modname)
  File "C:\Code\Zope\lib\python\AccessControl\tests\testAcquisition.py",
line 25, in ?
    Zope2.startup()
  File "C:\Code\Zope\lib\python\Zope2\__init__.py", line 47, in startup
    _setconfig()
  File "C:\Code\Zope\lib\python\Zope2\Startup\run.py", line 50, in _setconfig
    handlers.handleConfig(opts.configroot, opts.confighandlers)
  File "C:\Code\Zope\lib\python\Zope2\Startup\handlers.py", line 208,
in handleConfig
    return multihandler(handlers)
TypeError: 'NoneType' object is not callable

An "easier" failure occurs if "-v" is passed to test.py:

C:\Code\Zope>\python23\python.exe test.py -v
Running unit tests at level 1
Running unit tests from C:\Code\Zope\lib\python
Error: option -v not recognized
For help, use test.py -h


OTOH, it may "really" be the fault of testAcquistion.py, which contains

"""
import Zope2
Zope2.startup()
"""

at module(!) level.  test.py imports a lot of stuff, and it seems
pretty crazy to me for a test file to start Zope as a side effect of
merely being imported.  Then again, many Zope test files do the same
thing.


More information about the Zope-Checkins mailing list