On Wed, Mar 04, 2009 at 12:16:53PM -0800, Marek Szuba wrote: -> roups.com> -> - it is presently necessary to run 'setup.py built_ext -i' to make -> Pygr run correctly. Why not just 'build', like before? And will -> 'install' work?
build_ext -i is more convenient for development, because you can make changes to Python files & test them without running any other command. If you use runtest -b it will look in the build directory instead. -> - IMHO it would make more sense for all_tests mode of runtest.py to -> look for test scripts in the directory it is in rather than the -> current one, as it allows something like "python pygr/tests/ -> runtest.py" to work; all it takes to get this to work is to replace -> -> mods = os.listdir(os.getcwd()) -> -> with -> -> mods = os.listdir(os.path.dirname(sys.argv[0])) -> -> in runtest.py. I've tested this on leelab2 and it works fine. You can also use runtest.__file__, so no need to look at sys.argv[0]. I think this is a good change. cheers, --titus -- C. Titus Brown, [email protected] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
