[issue5716] Overzealous deprecation of BaseException.message

Ezio Melotti added the comment: Closing this as a duplicate of #6844. -- nosy: +ezio.melotti resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> BaseException DeprecationError raises inappropriately ___ Pyth

[issue5716] Overzealous deprecation of BaseException.message

Alan Isaac added the comment: FYI a patch has been committed that should fix this. For discussion see http://bugs.python.org/issue6844 -- nosy: +aisaac ___ Python tracker ___ ___

[issue5716] Overzealous deprecation of BaseException.message

Changes by Francis Devereux : -- nosy: +frankoid ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue5716] Overzealous deprecation of BaseException.message

Changes by Nick Coghlan : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue5716] Overzealous deprecation of BaseException.message

Steven Bethard added the comment: I've run into exactly the same thing. The argparse module's ArgumentError had a "message" attribute back in Python 2.4, and in Python 2.6 I get the same warnings Tres is getting. -- nosy: +bethard ___ Python tracker

[issue5716] Overzealous deprecation of BaseException.message

New submission from Tres Seaver : 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 Ba