On 11-Apr-2009, Julian Andres Klode wrote: > I am attaching the current state of a apt.deprecation module, which > will be used for this. This can be used for apt.** and aptsources.*, > but not for apt_pkg and apt_inst. As you can see, parts are written > by you. Thanks, I'm glad that it's proven useful. I do hope the test code gets separated out to a unit test module though :-) > For apt_pkg and apt_inst, I am not sure how to do this. Being > written in C++, it may be to hard to warn about every deprecated > method and attribute. I had a look at the C++ interfaces and couldn't see how to do the right thing for the implementation, so I don't have an opinion there. > Therefore, I suggest that we just warn on using the top-level > functions like GetCache() and not every where else. So long as the whole external interface is PEP 8 conformant, that sounds fine. -- \ “[Entrenched media corporations will] maintain the status quo, | `\ or die trying. Either is better than actually WORKING for a | _o__) living.” —ringsnake.livejournal.com, 2007-11-12 | Ben Finney <ben@benfinney.id.au>
Attachment:
signature.asc
Description: Digital signature