Just updating my book to using the django 1.7 beta. I use LiveServerTestCase a lot.
I used to rely on the fact that LiveServerTestCase "magically" serves static files from app folders. I see the default functionality is that this no longer works, but I can get it by switching to StaticLiveServerTestCase. great, glad to see that was built for backwards compatibility, I'll switch to using that, so no immediate problem. i am, as always, eternally gratefully to everyone involved for their thoughtfulness. But I just wanted to express the fact that it feels a little counter-intuitive. I don't know enough to weigh how important it is to remove a dependency on a contrib app from the testcases framework, but, as a user, having to remember that i need to run `collectstatic` before all my tests will pass is a bit weird. collectstatic is something i do on servers, not on my local dev box. and LiveServerTestCase isn't much use without working static files. So I guess I'm saying, how about just moving LiveServerTestCase into contrib, and merging it with StaticLiveServerTestCase?? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c0868046-2147-486b-8c2c-06f3cd5ca8af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
