Bugs item #880951, was opened at 2004-01-21 00:03 Message generated for change (Comment added) made by lemburg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=880951&group_id=5470

Category: Unicode Group: Feature Request Status: Open Resolution: None Priority: 5 Submitted By: Jon Willeke (willeke) Assigned to: M.-A. Lemburg (lemburg) Summary: "ez" format code for ParseTuple()

Initial Comment: I'm using Python 2.3.3 on SuSE Linux 8.2.

It would be nice to have an "ez" format code that is to "es" as "z" is to "s". Whereas the "s" and "z" codes depend on the default encoding, "es" lets you specify the encoding, which is useful for interfacing with GTK+ and GNOME libraries, which have largely standardized on UTF-8.

I think it is possible to simulate the desired behavior with "O&", but it would be simpler with "ez".

----------------------------------------------------------------------

Date: 2004-03-25 18:41

Message: Logged In: YES user_id=38388

Can you elaborate on the use case ? I'm asking because I don't find the 'z' code particulary useful myself because there are more elegant ways to deal with optional arguments.

----------------------------------------------------------------------

Comment By: Jon Willeke (willeke) Date: 2004-01-22 00:29

Message: Logged In: YES user_id=185468

I'm attaching a patch that adds support for the "ez" and "ez#" format codes.

----------------------------------------------------------------------