On Friday 12 March 2004 05:40 am, yuppie wrote:
> I don't care much *how* this is resolved, but I'd like to have this
> consistent and up to date. If I always have to check if the python
> version is set correctly that line isn't helpful at all.
Well, Tres appearantly hasn't had time to respond
Hi!
Fred Drake wrote:
On Thursday 11 March 2004 10:40 am, Tres Seaver wrote:
> #!/usr/bin/python2.3
>
> distutils will munge it anyway, if it installs the scripts.
That won't work for a lot of developers, I'll bet, who have python2.3
installed in /usr/local/bin. The "env hack" is more reasona
On Thursday 11 March 2004 10:40 am, Tres Seaver wrote:
> #!/usr/bin/python2.3
>
> distutils will munge it anyway, if it installs the scripts.
That won't work for a lot of developers, I'll bet, who have python2.3
installed in /usr/local/bin. The "env hack" is more reasonable for
developers; s
yuppie wrote:
So you propose to replace *all* the #! lines by
#!/usr/bin/env python2.3
#!/usr/bin/python2.3
distutils will munge it anyway, if it installs the scripts.
Tres.
--
===
Tres Seaver[EMAIL PROT
Hi!
Tres Seaver wrote:
yuppie wrote:
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\
yuppie wrote:
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?
Hi!
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 sur
On Wed, 2004-03-10 at 13:39, Evan Simpson wrote:
> Jeremy Hylton wrote:
> > Make sure App.Product is imported first, so that test.py can work.
> >
> > This change does not affect the old utilities/testrunner.py.
>
> This checkin message caused me to notice 'test.py' for the first time.
> Can you
