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. * Some docs need adding to the 1.2 release notes. * 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. If it is deprecated, what is the migration path? It really would need to be specified in painstaking detail. Other than that, I think the PendingDeprecationWarnings are OK. Regards, Luke -- I never hated a man enough to give him his diamonds back. (Zsa Zsa Gabor) Luke Plant || http://lukeplant.me.uk/ -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en.
