Incorrect type in PyDict_Next() example code

[jasonevans]

BPO	1629125
Nosy	@birkenfeld

^{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 2007-01-17.21:20:53.000>
created_at = <Date 2007-01-05.23:15:47.000>
labels = ['docs']
title = 'Incorrect type in PyDict_Next() example code'
updated_at = <Date 2007-01-17.21:20:53.000>
user = 'https://bugs.python.org/jasonevans'

bugs.python.org fields:

activity = <Date 2007-01-17.21:20:53.000>
actor = 'georg.brandl'
assignee = 'nnorwitz'
closed = True
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2007-01-05.23:15:47.000>
creator = 'jasonevans'
dependencies = []
files = []
hgrepos = []
issue_num = 1629125
keywords = []
message_count = 2.0
messages = ['30934', '30935']
nosy_count = 3.0
nosy_names = ['nnorwitz', 'georg.brandl', 'jasonevans']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1629125'
versions = []

[jasonevans]

In the PyDict_Next() documentation, there are two example snippets of code. In both snippets, the line:

    int pos = 0;

should instead be:

ssize_t pos = 0;

or perhaps:

    Py_ssize_t pos = 0;

On an LP64 system, the unfixed snippets will cause a compiler warning due to size mismatch between int and ssize_t.

Using Python 2.5 on RHEL WS 4, x86_64.

[birkenfeld]

Yep, it has to be Py_ssize_t. Fixed in rev. 53477, 53478 (2.5).