PyNode_New() does not initialize n->n_col_offset

[TomaszPytel]

BPO	40502
Nosy	@nanjekyejoannah
PRs	bpo-40502: Initialize n->n_col_offset #19988

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2020-05-08.21:01:31.450>
created_at = <Date 2020-05-04.18:26:58.199>
labels = ['interpreter-core', '3.9']
title = 'PyNode_New() does not initialize n->n_col_offset'
updated_at = <Date 2020-05-08.21:01:31.449>
user = 'https://bugs.python.org/TomaszPytel'

bugs.python.org fields:

activity = <Date 2020-05-08.21:01:31.449>
actor = 'nanjekyejoannah'
assignee = 'none'
closed = True
closed_date = <Date 2020-05-08.21:01:31.450>
closer = 'nanjekyejoannah'
components = ['Interpreter Core']
creation = <Date 2020-05-04.18:26:58.199>
creator = 'Tomasz Pytel'
dependencies = []
files = []
hgrepos = []
issue_num = 40502
keywords = ['patch']
message_count = 2.0
messages = ['368074', '368464']
nosy_count = 2.0
nosy_names = ['nanjekyejoannah', 'Tomasz Pytel']
pr_nums = ['19988']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue40502'
versions = ['Python 3.9']

[TomaszPytel]

I found this by accident by compiling empty strings since I use column information from the AST tree, if not initialized I get a starting column of -842150451. The easy fix is to initialize n->n_col_offset = 0; in Parser/node.c:PyNode_New().

[nanjekyejoannah]

New changeset d10091a by Joannah Nanjekye in branch 'master':
bpo-40502: Initialize n->n_col_offset (GH-19988)
d10091a