How about 'G'? (Giant, or perhaps gynormous, integer?)
Then I could also map 'g' to the signed version (same as L) for consistency. On Thu, Mar 15, 2012 at 11:49 AM, Benjamin Peterson <benja...@python.org>wrote: > 2012/3/15 Gil Colgate <gcolg...@gmail.com>: > > We use a lot of UnsignedLongLongs in our program (ids) and have been > parsing > > in PyArg_ParseTuple with 'K', which does not do error checking. > > I am planning to add a new type to our local build of python for parsing > > Unsigned Long Longs (64 bit numbers) that errrors if the number has more > > than the correct number of bits. > > > > I am thinking to use the letter 'N' for this purpose, since l,k,K,U,u are > > all taken. > > Unfortunately, the would conflict with Py_BuildValue's 'N'. > > > > -- > Regards, > Benjamin >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
