[issue3295] PyExc_BufferError is declared but nowhere defined

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: On Wed, Jul 30, 2008 at 6:46 PM, Antoine Pitrou <[EMAIL PROTECTED]> wrote: > > Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > > About r65312, BufferError inherits from StandardError, not directly from > Exception :) [ Benjamin sla

[issue3295] PyExc_BufferError is declared but nowhere defined

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: About r65312, BufferError inherits from StandardError, not directly from Exception :) ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3295] PyExc_BufferError is declared but nowhere defined

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: ... and backported to the trunk in r65310. ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3295] PyExc_BufferError is declared but nowhere defined

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: Done in r64751. -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3295] PyExc_BufferError is declared but nowhere defined

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: The following patch fixes it. -- keywords: +patch nosy: +teoliphant Added file: http://bugs.python.org/file10821/buffererror.patch ___ Python tracker <[EMAIL PROTECTED]>

[issue3295] PyExc_BufferError is declared but nowhere defined

New submission from Antoine Pitrou <[EMAIL PROTECTED]>: Astonishingly, PyExc_BufferError is defined in pyerrors.h but it is defined nowhere. Consequently, any piece of code raising a PyExc_BufferError will cause the interpreter to crash as soon as it tries to do something with the exception... -