On Mon, Nov 2, 2009 at 1:28 PM, Min <[email protected]> wrote: > > Alright, so upgrading to 1.0.9 seemed to have no effect. However, the > command "python setup.py test" command works in running the unittests. > Now, the only problem I'm having is that due to the quantity of the > tests, I can't see all the results in the command prompt window after > the tests are run. I did get around this by moving to the folder where > a subset of the test files are saved, then calling the same command, > using a slightly modified setup.py. > > However, I'm wondering if there's a way for me to catch the outputs to > the command prompt (using "> log.txt" after the command doesn't seem > to work) or to call the command while specifying which folder or files > to look for tests in. Adding to the command the path to the folder > with some tests in it didn't seem to do anything. > > You can redirect stderr with "2> log.txt", or redirect both stdout & stderr with: python setup.py test 2> log.txt 2>&1
BTW, does working with a subset of your tests help with the nose problem? Did you ever try different versions of nose? Does falling back to nose 0.9.3 resolve it? How about starting a clean virtualenv? There's no "turbogears" directory in your project, is there? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
