#20165: Doc test example may lead to programmer errors
-------------------------------+--------------------------------------
     Reporter:  lorinh         |                    Owner:  nobody
         Type:  Uncategorized  |                   Status:  new
    Component:  Documentation  |                  Version:  master
     Severity:  Normal         |               Resolution:
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  1              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  1
-------------------------------+--------------------------------------

Comment (by lorinh):

 Replying to [comment:2 aaugustin]:
 > What is the difference with #15896?


 My understanding is that #15896 was based on a misunderstanding about the
 difference between django.utils.unittest.TestCase and
 django.test.TestCase, and so the author claimed (incorrectly) that there
 was a bug in the test example.

 I'm suggesting that the test example, while technically correct, could be
 improved in a way that would reduce the likelihood of future programmer
 errors.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/20165#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to