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

Showing content from https://mail.python.org/pipermail/python-dev/2000-February/002311.html below:

[Python-Dev] using ":name" in ParseTuple()

• Previous message: [Python-Dev] using ":name" in ParseTuple()
• Next message: [Python-Dev] Whither cursesmodule?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, 24 Feb 2000, Skip Montanaro wrote:
>...
> Is it just adding
> ":public_name" to any and all format strings we can find?  I'm going to have
> a little evening time free off-net while I'm out of town for the next week.
> I will freshen up my CVS copy and try doing a bunch.

Yup. That's all there is.

For example, consider line 1013 in stringobject.c (string_lower function):

today:
	if (!PyArg_ParseTuple(args, ""))

change to:
	if (!PyArg_ParseTuple(args, ":lower"))

The :name part should be the user-visible name of the function or method.
It does get tricky with something like the string_rfind_internal function
-- the ParseTuple call is used for several functions.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

• Previous message: [Python-Dev] using ":name" in ParseTuple()
• Next message: [Python-Dev] Whither cursesmodule?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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