Jeremy Hylton wrote:
test.py obsoleted testrunner.py as of Zope 2.7.  test.py was being used
by ZODB3 and Zope3 for a while before it was added to Zope 2.7.

Why does setup.py still install testrunner.py, not test.py?

And BTW: Could *all* files necessary to run tests be installed?

I'm not sure which #! line you mean, but I think you're right to say it
should be python 2.3.  All the software on the head requires python 2.3.

Some grep results from Zope HEAD:

setup.py:                     #! /usr/bin/env python
test.py:                      #! /usr/bin/env python2.2
utilities\check_catalog.py:   #!/usr/bin/env python2.1
utilities\requestprofiler.py: #!/usr/bin/env python
utilities\compilezpy.py:      #!/usr/bin/env python
utilities\zpasswd.py:         #!/usr/bin/env python
utilities\testrunner.py:      #! /usr/bin/env python2.2
utilities\ZODBTools\space.py: #! /usr/bin/env python

And many tests, some of them still with python1.5, e.g.

lib\python\TAL\tests\run.py: #! /usr/bin/env python1.5

Could we have a policy for this? I guess '#! /usr/bin/env python' is easier to keep up to date ...

Cheers, Yuppie

Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )

Reply via email to