#12226: Test HttpResponse template attribute needlessly hard to use
----------------------------------------+-----------------------------------
Reporter: carljm | Owner: carljm
Status: new | Milestone:
Component: Testing framework | Version: SVN
Resolution: | Keywords: sprintSep2010
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Changes (by carljm):
* keywords: => sprintSep2010
* owner: nobody => carljm
* has_patch: 0 => 1
* version: 1.1 => SVN
Comment:
Attached patch starts response.template on deprecation path with
PendingDeprecationWarning, and adds response.templates API that is always
a list, whether empty, length 1, or longer.
I wasn't sure what the policy is for tests in a case like this. The patch
includes conversion of most tests to the new API, and addition of a couple
new tests to verify the back-compat API still works. Alternatively, the
current trunk tests still all pass unchanged if only the non-test portion
of the patch is applied, so if the policy is to wait to convert tests
until PendingDeprecation becomes Deprecation, that's easily done as well.
Git branch (same as patch) at
http://github.com/carljm/django/commits/ticket_12226
--
Ticket URL: <http://code.djangoproject.com/ticket/12226#comment:2>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
