Cool, thanks On Sep 20, 3:30 pm, Carl Meyer <carl.j.me...@gmail.com> wrote:
> 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. Cool, thank you Carl. I'll go ahead and submit it as a ticket and let it take its natural course from there. > 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. Yeah, that's what I was thinking too. Maybe other people will have examples where it might cause some critical issues, I guess we'll see. -- 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.
