[issue6240] API to get source encoding as defined by PEP 263
report at bugs.python.org
Mon Jun 8 21:01:45 CEST 2009
New submission from Sridhar Ratnakumar <sridharr at activestate.com>:
It'd be nice to get the encoding used by a specific Python file.
Considering that 'print' uses sys.stdout.encoding which is always set to
None when the Python process is run by subprocess, knowing the source
encoding is absolutely necessary in decoding the output generated by
eg: Run 'python setup.py --author' in the python-wifi-0.3.1 source
package as a subprocess.Popen(...) call.. and print the stdout.read()
string; you'll get encoding error.. unless you do
stdout.read().decode('latin1') .. where latin1 is specified as a coding:
line in setup.py.
The following function tries to detect the coding, but this guess work
not necessary when this is integrated with the standard library whose
implementation maps directly to that of PEP 263.
+ """Detect the encoding used in the file ``python_file``
+ Detection is done as per http://www.python.org/dev/peps/pep-0263/
+ first_two_lines = open(python_file).readlines()[:2]
+ coding_line_regexp = ".*coding[:=]\s*([-\w.]+).*"
+ for line in first_two_lines:
+ m = re.match(coding_line_regexp, line)
+ if m:
+ return m.group(1)
+ # if no encoding is defined, use the default encoding
+ return 'ascii'
subprocess encoding mess: http://bugs.python.org/issue6135
components: Interpreter Core, Library (Lib)
nosy: lemburg, loewis, srid
title: API to get source encoding as defined by PEP 263
type: feature request
versions: Python 2.7, Python 3.1, Python 3.2
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list