Adding a hidden field to BaseException going to break the ABI?
issue6844 wants to stop a warning from being raised when someone accesses a 'message' attribute on an exception when it is set by the user (currently any usage of the 'message' attribute raises a warning). To do this properly is going to require some state flag on BaseException's struct. But I don't know if that constitutes breaking the ABI during a micro release or not. I figure no but I wanted to double-check.
-Brett
2009/9/13 Brett Cannon <brett@python.org>:
issue6844 wants to stop a warning from being raised when someone accesses a 'message' attribute on an exception when it is set by the user (currently any usage of the 'message' attribute raises a warning). To do this properly is going to require some state flag on BaseException's struct. But I don't know if that constitutes breaking the ABI during a micro release or not. I figure no but I wanted to double-check.
Is the BaseException struct public?
-- Regards, Benjamin
On Sun, Sep 13, 2009 at 13:30, Benjamin Peterson <benjamin@python.org> wrote:
2009/9/13 Brett Cannon <brett@python.org>:
issue6844 wants to stop a warning from being raised when someone accesses a 'message' attribute on an exception when it is set by the user (currently any usage of the 'message' attribute raises a warning). To do this properly is going to require some state flag on BaseException's struct. But I don't know if that constitutes breaking the ABI during a micro release or not. I figure no but I wanted to double-check.
Is the BaseException struct public?
Only in so far as PyExc_BaseException is documented for use with PyErr_*() and inheritance.
-Brett
participants (2)
-
Benjamin Peterson -
Brett Cannon