Can someone explain the test condition on line 31 of https://github.com/django/django/blob/master/django/contrib/staticfiles/views.py - Just spent a few hours trying to get my unit tests to pass and couldn't figure out what was going on until I found this weirdness.
--
-- I understand serve() isn't meant for production but, prior to having production ready it's nice to be able to unit test my code as it's being developed with serve() as a temporary measure. Right now I'm using serve() as a temporary hack to stand in for an external URI router that isn't present yet. Throwing a 404 without any helpful indication of the true cause of the exception simply confuses people and makes them wonder why the URI they're passing in is not being found when they can try it on the command line and see it work just fine. At minimum this exception should be more explicit.
Chief Systems Architect Proteus Technologies
Chief Fan Biggest Fan Productions
Personal blog where I am not your demographic.
This email intended solely for those who have received it. If you have received this email by accident - well lucky you!!
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAHN%3D9D5U0gtKym4Er5hBURwhJ2aC_zteUthVR4Rq5-7EDrMkYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment