[Pyrex] Pyrex testing

[Scott Jackson]

Sorry, I forgot to send this to the list. In addition:

Traceback (most recent call last):
  File "Testing.py", line 27, in <module>
    from Pyrex.Unix.LinuxSystem import c_compile
  File
"/home/builder/programs/lib/python2.5/site-packages/Pyrex-0.9.5.1a.001.dev200707251128-py2.5.egg/Pyrex/Unix/LinuxSystem.py", line 14, in <module>
    version = "%s.%s" % sys.version[:2]
NameError: name 'sys' is not defined


On Fri, 2007-07-27 at 12:48 +1200, Greg Ewing wrote:
> Hmmm. I'm not sure why I used pythonw there -- it
> shouldn't be necessary.
> 

--- ./bin/run_tests     2007-07-27 09:36:16.000000000 -0500
+++ ./bin/run_tests     2007-07-27 09:35:20.000000000 -0500
@@ -1,4 +1,4 @@
-#!/usr/bin/env pythonw
+#!/usr/bin/env python
 #
 #   runtests -- Run all the tests.
 #

:)

> You may need to adjust your PYTHONPATH so that it
> makes the Pyrex directory available as an importable
> package.
Well, importing Pyrex works fine, and running the primes/spam demos work
fine (I don't have Numeric)- let me clarify a little bit:
I untar the pyrex ball into my homedir and attempt to run run_tests from
inside the directory. I've got Pyrex installed as an egg, which means
that it's automatically added to my PYTHONPATH. One thing I could forsee
is that when it tries to load Pyrex.Testing, this exists within the
testing tarball and not in the Pyrex package:
<eggdir>/Pyrex/*
vs
<homedir>/Pyrex-x.y.z.q/Testing/*
I'm not sure this is the problem but even if it is, I'm a bit in the
dark about how I would go about fixing it.

-- 
Scott Jackson <scott.jackson at enthought.com>
Enthought, Inc.