Question: This code:

```
for root, dirs, files in os.walk('.'):
    print(root)

```

Gives me this error:

```
UnicodeEncodeError: 'utf-8' codec can't encode character '\udcc3' in position 27: surrogates not allowed

```

How do I walk through a file tree without getting toxic strings like this?

Answer: 
On Linux, filenames are 'just a bunch of bytes', and are not necessarily encoded in a particular encoding. Python 3 tries to turn everything into Unicode strings. In doing so the developers came up with a scheme to translate byte strings to Unicode strings and back without loss, and without knowing the original encoding. They used partial surrogates to encode the 'bad' bytes, but the normal UTF8 encoder can't handle them when printing to the terminal.

For example, here's a non-UTF8 byte string:

```
>>> b'C\xc3N'.decode('utf8','surrogateescape')
'C\udcc3N'

```

It can be converted to and from Unicode without loss:

```
>>> b'C\xc3N'.decode('utf8','surrogateescape').encode('utf8','surrogateescape')
b'C\xc3N'

```

But it can't be printed:

```
>>> print(b'C\xc3N'.decode('utf8','surrogateescape'))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeEncodeError: 'utf-8' codec can't encode character '\udcc3' in position 1: surrogates not allowed

```

You'll have to figure out what you want to do with file names with non-default encodings. Perhaps just encoding them back to original bytes and decode them with unknown replacement. Use this for display but keep the original name to access the file.

```
>>> b'C\xc3N'.decode('utf8','replace')
C�N

```

`os.walk` can also take a byte string and will return byte strings instead of Unicode strings:

```
for p,d,f in os.walk(b'.'):

```

Then you can decode as you like.
Filter with `sed` or `grep`:

```
set | sed -n '/^[a-zA-Z0-9_]*=/p'
# ... or ...
set | grep '^[a-zA-Z0-9_]*='
# ... or ...
set | egrep '^[_[:alnum:]]+='

```

This is sensitive to how crazy your variable names are. The last version should handle most crazy things.