Add unsigneds to ParseTuple/BuildValue

[gvanrossum]

BPO	454896
Nosy	@gvanrossum

^{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 2002-06-10.21:18:14.000>
created_at = <Date 2001-08-24.09:10:32.000>
labels = ['type-feature']
title = 'Add unsigneds to ParseTuple/BuildValue'
updated_at = <Date 2002-06-10.21:18:14.000>
user = 'https://github.com/gvanrossum'

bugs.python.org fields:

activity = <Date 2002-06-10.21:18:14.000>
actor = 'gvanrossum'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['None']
creation = <Date 2001-08-24.09:10:32.000>
creator = 'gvanrossum'
dependencies = []
files = []
hgrepos = []
issue_num = 454896
keywords = []
message_count = 2.0
messages = ['53244', '53245']
nosy_count = 1.0
nosy_names = ['gvanrossum']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue454896'
versions = []

[gvanrossum]

From: David Beazley <beazley@cs.uchicago.edu>

Since "integers" can now have arbitrary precision and
can represent large unsigned values, can you add three
new format characters to PyArg_ParseTuple() and
Py_BuildValue() for the C datatypes "unsigned int",
"unsigned long", and "unsigned long long"?

The "u" and "l" namespace is a little crowded (and I
don't think you would want to break that). However,
here's one idea:

'I' - unsigned int (consistent with H and B)
'p' - unsigned long ('p' is for positive)
'P' - unsigned long long

[gvanrossum]

Logged In: YES
user_id=6380

Thank you.

I've moved this feature request to PEP-42, "Feature Requests".