[issue3304] invalid call to PyMem_Free() in fileio_init()

Neal Norwitz <[EMAIL PROTECTED]> added the comment: In 3.0 the free is necessary, though see http://bugs.python.org/issue3662 . -- nosy: +nnorwitz status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3304] invalid call to PyMem_Free() in fileio_init()

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: thanks. fixed in trunk r64758. i'm assuming that'll be merged into py3k automagically. -- resolution: -> accepted versions: +Python 3.0 -Python 2.6 ___ Python tracker <[EMAIL PROTECTED]>

[issue3304] invalid call to PyMem_Free() in fileio_init()

Changes by Gregory P. Smith <[EMAIL PROTECTED]>: -- assignee: -> gregory.p.smith keywords: +easy nosy: +gregory.p.smith priority: -> normal ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3304] invalid call to PyMem_Free() in fileio_init()

New submission from STINNER Victor <[EMAIL PROTECTED]>: fileio_init() calls PyMem_Free(name); whereas name comes from PyArg_ParseTupleAndKeywords(). Attached patch removes this invalid call. The bug may also affect Python3.0. -- components: Library (Lib) files: fileio_pymem_free.patch