bin/test.py should be called bin/test

[Daniel Nouri]

Zope3 has bin/test probably because of the same issue. When some test tries to import the 'test' Python standard module, they get back the test script. If we call it ``test``, this problem will be gone.

When running my zope.testbrowser tests I get the following:

Traceback (most recent call last):
  File "test_doctests.py", line 19, in ?
  File "/home/daniel/devel/z29-instances/plone25/Products/PasswordResetTool/tests/utils/__init__.py", line 2, in ?
    from testbrowser import Browser
  File "/home/daniel/devel/z29-instances/plone25/Products/PasswordResetTool/tests/utils/testbrowser.py", line 13, in ?
    from zope.testbrowser import testing
  File "/home/daniel/lib/Zope-2.9.2//lib/python/zope/testbrowser/__init__.py", line 19, in ?
    from testing import Browser
  File "/home/daniel/lib/Zope-2.9.2//lib/python/zope/testbrowser/testing.py", line 25, in ?
    from zope.testbrowser import browser
  File "/home/daniel/lib/Zope-2.9.2//lib/python/zope/testbrowser/browser.py", line 19, in ?
    from test import pystone
  File "/home/daniel/lib/Zope-2.9.2/bin/test.py", line 94, in ?
    help="""\
  File "/usr/lib/python2.4/optparse.py", line 939, in add_option
    self._check_conflict(option)
  File "/usr/lib/python2.4/optparse.py", line 914, in _check_conflict
    option)
OptionConflictError: option --config-file: conflicting option string(s): --config-file

[Daniel Nouri (daniel.nouri)]

This seems to work well for 'In-Place' instances.

[Hanno Schlichting (hannosch)]

Current Zope releases don't contain the test.py module anymore but have switched to external test runners, like the buildout based zc.recipe.testrunner.