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/2000-February/002308.html below:

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

[Python-Dev] using ":name" in ParseTuple()Greg Stein gstein@lyra.org
Thu, 24 Feb 2000 13:52:31 -0800 (PST)
If anyone out there is looking for some straight-forward changes to help
with Python development, then here is a chance...

I'll get around to submitting patches for this, but it would be much
later. So, if somebody can beat me to it...

Cheers,
-g

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

---------- Forwarded message ----------
Date: Thu, 24 Feb 2000 16:42:12 -0500
From: Guido van Rossum <guido@python.org>
To: Greg Stein <gstein@lyra.org>
Cc: python-checkins@python.org
Subject: Re: [Python-checkins] CVS: python/dist/src/Objects listobject.c,2.63,
    2.64

> On a separate track, how about using the ":Name" form in the ParseTuple
> calls? It improves the error response a bit more...
> 
> Is that something you'd want to see in all the ParseTuple calls?

Ah, darn.  I tried ";message" but it's inferior; I'd forgotten about
":name".  Yes, that should be standard...  Patches, please?

--Guido van Rossum (home page: http://www.python.org/~guido/)

_______________________________________________
Python-checkins mailing list
Python-checkins@python.org
http://www.python.org/mailman/listinfo/python-checkins




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