On Sun, 3 May 2009 12:12:23 -0700 (PDT) michel bellis <fill.i...@9online.fr> wrote:
> when I run the test from the folder where I made the build I get this > message : > 'unable to import extension module: cannot import name cnestedlist' Guys, I'm getting more and more convinced that we should make build-directory mode the default for running tests after all. Not sure if you've noticed but almost EVERY non-developer posting here runs into this. A more descriptive error message will only help such users resolve the problem without posting to pygr-dev - but not stop them from cringing when they run into something they find counter-intuitive. IMHO a logical way of doing this is to add a new target for setup.py, "test", which will depend on "build" and call runtest -b after the build directory has been filled, forcing runtest to try to load Pygr from that directory *only*. This would have at least the following benefits: - unification - all three stages are launched using the same syntax, much like 'make; make test; make install' when working with GNU Autoconf; - intuitiveness - no "why do I have to run both 'build' AND 'build_ext -i'?" annoyance; - when called by hand, runtest.py would work the same way as before. The question is whether it is possible to "lock Python down" so that doesn't try to load Pygr from anywhere else but the build directory. Can we? -- MS --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@googlegroups.com To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
