Hi all,

So I'm currently trying to write some tests for a subtle issue
involving resolving imports and cimports. (I think I emailed about
this a while back.) The particular issue isn't so important right this
minute -- the only thing that matters is that to test it, I need a
test with a few layers of directories, with __init__.py files
sprinkled in several places, and potentially *not* at the root.
Unfortunately, this doesn't work so well with the current testing
setup -- at least, as I understand, there's no way to tell it "when
you try to run this test, also copy along this particular chunk of the
current directory." So there are two obvious choices:

1) Give a test a way of specifying what other files should come along
as part of it.
2) Create a directory called nested (or something else) somewhere in
the tests/ tree (maybe one for each of the current subdirectories?),
and add code to runtests.py to handle that whole tree at once.

Each of these has its ups and downs -- but I'd love it if someone told
me that the testing code already did what I'm looking for, and I just
didn't know it. ;) I think (1) feels like the "classier" solution, but
(2) would make it easy for someone to *add* a nested test without
having to create a whole bunch of files/directories themselves. That
said, we'd have to be careful that no one accidentally broke a test by
modifying it -- tests really should be nearly immutable.

Any thoughts?

-cc
_______________________________________________
Cython-dev mailing list
Cython-dev@codespeak.net
http://codespeak.net/mailman/listinfo/cython-dev

Reply via email to