Re: unittest.TestCase vs. django.test.TestCase in overview example

I created a Django Trac ticket for this: https://code.djangoproject.com/ticket/20165 On Saturday, March 30, 2013 11:30:44 PM UTC-4, Brian Schott wrote: > > There is really a bigger question in my mind about the appropriateness of > using django.utils.unittest in the testing overview section.

Re: unittest.TestCase vs. django.test.TestCase in overview example

There is really a bigger question in my mind about the appropriateness of using django.utils.unittest in the testing overview section. It is an optimization that the warning admits is fairly limited for real testing and is premature for the first example. It would be better to break out the

Re: unittest.TestCase vs. django.test.TestCase in overview example

Will dropping support for Python 2.6 have any effect here? I assumed the example would just switch to using unittest.TestCase instead of django.utils.unittest.TestCase, and the usability issue would remain. I think having the warning above the example would help, but I'd still prefer having

Re: unittest.TestCase vs. django.test.TestCase in overview example

It seems like it could be a dangerous precedent to cater to people who don't take the time to fully read the docs, but in this case I'm a bit sympathetic. On the other hand, this example will probably be a bit more obvious when we drop support for Python 2.6 and no longer have

unittest.TestCase vs. django.test.TestCase in overview example

Hi there: On the Django testing overview doc page , the initial example uses unittest.TestCase. A Django developer who was looking for a quick reminder on how to write unit tests is likely to hit this page first. If that