A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2001-November/018730.html below:

[Python-Dev] PyArg_ParseTuple and unicode

[Python-Dev] PyArg_ParseTuple and unicode [Python-Dev] PyArg_ParseTuple and unicodeJack Jansen jack@oratrix.nl
Tue, 27 Nov 2001 13:04:39 +0100
I had expected the PyArg_ParseTuple() "u" specifier to automatically convert 
string objects to unicode strings with the default encoding (just as the 
reverse is true for "s"), but to my surprise it doesn't.

Is there a deep reason for this, or am I the first person to want this 
functionality? Or do I miss something and should I use a different format 
specifier?
--
Jack Jansen             | ++++ stop the execution of Mumia Abu-Jamal ++++
Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++
www.cwi.nl/~jack        | ++++ see http://www.xs4all.nl/~tank/ ++++





RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4