On Wed, Dec 17, 2008 at 8:31 AM, Martijn Faassen <faassen@startifact.com> wrote:
If we can get PendingDeprecationWarning working, people like Roger can keep refactoring without bothering too many people and still get the deprecation warnings they want to see. Then at some stage when a new release of a framework (Zope 3, Grok, Zope 2) is made, we could convert these warnings into true DeprecationWarnings and provide upgrade code for ZODB-level code. Or even not - the Grok project could for instance just have the policy not to release with any PendingDeprecationWarnings present either.
For things we know never get pickled, we could choose to use DeprecationWarning right away. This might run into Tres' issue, which I don't quite understand yet. :)
How does that sound?
Even though I don't mind deprecation warnings as they are, a provisional +1 from me; I too would like to hear more about Tres' scenario. -- Benji York Senior Software Engineer Zope Corporation