#14147: django 1.2 documentation refer to assertQuerysetEqual which is only
available in trunk
----------------------------------------+-----------------------------------
Reporter: djoume | Owner: nobody
Status: new | Milestone: 1.3
Component: Documentation | Version: 1.2
Resolution: | Keywords:
Stage: Ready for checkin | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Changes (by russellm):
* milestone: => 1.3
Comment:
If we follow the backwards compatibility policy strictly, we can't
introduce a new feature into 1.2; also, the feature doesn't (and can't)
exist in Django 1.2.0 or 1.2.1. It will appear in 1.2.2, by virtue of a
backported test case.
Strictly by the book, we should revert the changesets that need to use
assertQuerysetEqual. However, the overhead of maintaining two different
test suites (plus the speed boost associated with moving to unit tests) is
too much to ignore.
In the interests of practicality, I'm going to mark this as a "new in 1.3"
feature; it will exist as a feature in 1.2, but it will be a stealth
feature, and won't be documented.
--
Ticket URL: <http://code.djangoproject.com/ticket/14147#comment:3>
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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
