Hi Jim, On Sep 19, 1:19 am, "Jim D." <jim.dal...@gmail.com> wrote: > I found some time this evening to work this out, and have included a > revised patch for this proposal at the end of this message.
Thanks for your work on this! The usual Django workflow doesn't include patches to the mailing list: rather you can go ahead and open a Trac ticket and attach the patch there (even if you aren't sure of the approach yet), and reference the ticket number here. > * The addition of this feature required what I imagine to be a > significant change to test suite runner. Namely, I switched the order > of the build_suite() and setup_test_environment() methods in > run_tests(). So where this would break is if someone is doing a bit too much at import time of their tests module (like in the class body of a TestCase subclass): for instance, saving something to the database. I have to admit (gulp) that I have actually done this before and it currently works fine, but it's not really good practice and it's certainly not documented anywhere that you can do that, so personally I'm not sure it would be a problem to break it. Carl -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
