Hi All,

I'll answer multiple posts in here.

@Chris: this does not need to go into release 0.8, give me a few days
to see how quickly I can port the remaining tests (so far it was very
quick ... but I picked the easier ones first ;-0 ), I think by the end
of the week I can have everything ported.

@Titus: path munging is still in, as a separate module pathfix.py that
gets activated upon import. I think the order of imports should be
source directory, then build directory, then global because when
modifying pure python modules it is tedious to have to build first to
be able to test it. The build path is needed to load the extension
modules and for those you would need to build anyhow. The global path
is also needed (occasionally) because sometimes you want to test
whether pygr has been deployed correctly on a given system. I figure
out something useful here, maybe we can use a flag to the main test
runner to indicate that importing from non-source/non-build directory
is also ok.

@Nose: I do like nose and what it offers, and luckily we can use nose
with unittests. Where nose seem to cause complications is when you
need to decide what tests to run based on some conditions, at that
point the nose automation becomes a hindrance and now we need to work
against it. So I think we do not need to give up on nose, just not
make it the primary way to write the tests. This is pretty much in
line what you were saying so I think we are in agreement there.

> One problem I note is that, at least at the moment, runtest.py does not
> obviously fail even if one of the tests fails.

Yeah, this was an oversight, should be easy to fix because tests are
collected into a test suite (each test module implements a get_suite()
function that returns the battery of tests. Most often done by auto
discovery but in some cases uses code logic to determine what tests
should not be included), which then run through regular testrunners
that collect and return all the information we need.

In conclusion let me get back to you all in a few days and we'll take
a second look at how it goes.

Istvan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pygr-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to