[issue34539] namedtuple's exec() throws segmentation fault

Karthikeyan Singaravelan added the comment: Thanks Álvaro for the report and script. As part of triaging I am closing this as out of date since this bug seemed to have been fixed with issue34087 and is not reproducible on latest master and 3.7 branch. Feel free to reopen this if needed.

[issue34539] namedtuple's exec() throws segmentation fault

Álvaro Justen added the comment: Yes, I think it was fixed in https://bugs.python.org/issue34087 (didn't see the commits), I just wanted to report it because I don't know if a test for this specific case is needed (the other bug is not related to namedtuples). --

[issue34539] namedtuple's exec() throws segmentation fault

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34539] namedtuple's exec() throws segmentation fault

Raymond Hettinger added the comment: If this is only present in 3.7.0 and not in the current branches, it implies there was an exec() or ceval-loop bug in that release and it has been already fixed. This bug report may be out-of-date. -- ___

[issue34539] namedtuple's exec() throws segmentation fault

Álvaro Justen added the comment: I've cloned the cpython git repository and made fresh builds here: On v.3.6.6 (4cf1f54eb764f856fda5a394d8598c0c90d69d77) it works: $ git checkout v3.6.6 && ./configure && make && ./python --version && ./python namedtuple_bug.py [...compilation lines

[issue34539] namedtuple's exec() throws segmentation fault

Raymond Hettinger added the comment: The works for me. Can you try it on a fresh build or install of Python 3.7? -- nosy: +rhettinger ___ Python tracker ___

[issue34539] namedtuple's exec() throws segmentation fault

New submission from Álvaro Justen : I was working on a library called rows[https://github.com/turicas/rows] when a segmentation fault was thrown in the moment I've tried to read a CSV file. Since this part of the code is implemented completely in Python, I thought it could be a bug in Python