From 6f15e5796e89163bd9b5be7a3f7334d17f2c50c1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc-Andr=C3=A9=20Lemburg?= Date: Wed, 2 May 2001 17:16:16 +0000 Subject: Added new parser markers 'et' and 'et#' which do not recode string objects but instead assume that they use the requested encoding. This is needed on Windows to enable opening files by passing in Unicode file names. --- Doc/ext/ext.tex | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'Doc/ext/ext.tex') diff --git a/Doc/ext/ext.tex b/Doc/ext/ext.tex index 446802fd22..ba8217ec33 100644 --- a/Doc/ext/ext.tex +++ b/Doc/ext/ext.tex @@ -736,6 +736,12 @@ buffer and adjust \var{*buffer} to reference the newly allocated storage. The caller is responsible for calling \cfunction{PyMem_Free()} to free the allocated buffer after usage. +\item[\samp{et} (string, Unicode object or character buffer compatible +object) {[const char *encoding, char **buffer]}] +Same as \samp{es} except that string objects are passed through without +recoding them. Instead, the implementation assumes that the string +object uses the encoding passed in as parameter. + \item[\samp{es\#} (string, Unicode object or character buffer compatible object) {[const char *encoding, char **buffer, int *buffer_length]}] This variant on \samp{s\#} is used for encoding Unicode and objects @@ -767,6 +773,12 @@ overflow is signalled with an exception. In both cases, \var{*buffer_length} is set to the length of the encoded data without the trailing 0-byte. +\item[\samp{et\#} (string, Unicode object or character buffer compatible +object) {[const char *encoding, char **buffer]}] +Same as \samp{es\#} except that string objects are passed through without +recoding them. Instead, the implementation assumes that the string +object uses the encoding passed in as parameter. + \item[\samp{b} (integer) {[char]}] Convert a Python integer to a tiny int, stored in a C \ctype{char}. -- cgit v1.2.1