This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author turicas
Recipients rhettinger, turicas
Date 2018-08-29.14:25:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1535552758.17.0.56676864532.issue34539@psf.upfronthosting.co.za>
In-reply-to
Content
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 supressed...]
    Python 3.6.6

On the v.3.7.0 (1bf9cc509326bc42cd8cb1650eb9bf64550d817e) it segfaults:

    $ git checkout v3.7.0 && make clean && ./configure && make && ./python --version && ./python namedtuple_bug.py
    [...compilation lines supressed...]
    Python 3.7.0
    Segmentation fault

On the most recent 3.7 branch (65ef7425a32ee411d8047a4fad0fc6bb9ff733b1) it works:

    $ git checkout 3.7 && make clean && ./configure && make && ./python --version && ./python namedtuple_bug.py
    [...compilation lines supressed...]
    Python 3.7.0+

On master branch (2c8ddcf4f14f3e4c87a6fe6678ab5ad09130c6ab) it also works:

    $ git checkout master && make clean && ./configure && make && ./python --version && ./python namedtuple_bug.py
    [...compilation lines supressed...]
    Python 3.8.0a0

Note: I've tried to add a `print('works!')` at the end of the script, so we can see the result when it does not segfault, but adding this actually make it works on all versions; removing this line has the behaviour reported above.
History
Date User Action Args
2018-08-29 14:25:58turicassetrecipients: + turicas, rhettinger
2018-08-29 14:25:58turicassetmessageid: <1535552758.17.0.56676864532.issue34539@psf.upfronthosting.co.za>
2018-08-29 14:25:58turicaslinkissue34539 messages
2018-08-29 14:25:58turicascreate