On 21 Dec 2009, at 12:29, Luke Plant wrote: > On Sunday 20 December 2009 13:04:00 Ben Firshman wrote: >> Okay, I've updated the ticket with a new patch: >> >> http://code.djangoproject.com/ticket/12403 >> >> I wasn't sure on the extent of the depreciation warnings required, >> but hopefully that's the sort of thing needed. >> >> Thanks, >> >> Ben > > Some comments: > > * depreciated != deprecated. You mean the latter. There are various > instances of the former in comments and the names of test classes.
Whoops, you're absolutely right. > > * Some docs need adding to the 1.2 release notes. Righto. > > * What is going to happen to feeds.Feed? Is it deprecated or not? > (there is no PendingDeprecationWarning AFAICS). > I for one have a lot of code that uses feeds.Feed directly, > bypassing the 'high level' framework that provided the view > function. I wasn't sure whether to add a warning to that, since it is always used through the feed() view. Though to be clear, I've added one. > If it is deprecated, what is the migration path? It really > would need to be specified in painstaking detail. I've documented it in some detail in the release notes. Is this painstaking enough? New patch is attached to the ticket. Thanks for the feedback, Ben -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
