Message85695
I'm working on cleaning up deprecations for Zope and related
packages under Python 2.6. The irony here is that I'm receiving
deprecation warnings for custom exception classes which had a 'message'
attribute long before the abortive attempt to add them to the
BaseException type, which hardly seems reasonable.
For instance, docutils.parsers.rst defines a DirectiveError which takes
two arguments, 'level' and 'message', and therefore gets hit with the
deprecation (even though it never used the new signature). Likewise,
ZODB.POSException defines a ConflictError type which takes 'message' as
one of several arguments, all optional, and has since at least 2002.
I don't think either of these classes should be subject to a deprecation
warning for a feature they never used or depended on. |
|
Date |
User |
Action |
Args |
2009-04-07 12:07:06 | tseaver | set | recipients:
+ tseaver |
2009-04-07 12:07:06 | tseaver | set | messageid: <1239106026.05.0.616331762443.issue5716@psf.upfronthosting.co.za> |
2009-04-07 12:07:04 | tseaver | link | issue5716 messages |
2009-04-07 12:07:03 | tseaver | create | |
|