ctypes should support binary symbols.

Rationale: There's no requirement that the symbol name in question is encoded as ASCII or UTF-8.

>>> import ctypes
>>> t = type('iface', (ctypes.Structure,), {'_fields_': [(b'c_string_symbol', ctypes.CFUNCTYPE(ctypes.c_uint32))]})
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: '_fields_' must be a sequence of (name, C type) pairs

Field names define CField descriptor attributes on the class. Attribute names should be strings, not bytes. There's no syntactically clean way to use a bytes name. Consider the example of a generic property on a class:

    >>> T = type('T', (), {b'p': property(lambda s: 0)})
    >>> t = T()
    >>> t.p
    Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
    AttributeError: 'T' object has no attribute 'p'

    >>> getattr(t, b'p')
    Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
    TypeError: getattr(): attribute name must be string

We'd have to dig into the class dict and manually bind the property:

    >>> vars(T)[b'p'].__get__(t)
    0

Well, the original problem remains: symbol names aren't constrained to UTF-8 … so if I happen to stumble onto one of those (maybe generated by a code obfuscator), the answer is "don't use Python3 then"?

If you're automatically wrapping a C source file and don't know the source encoding, you could naively decode it as Latin-1. You're still faced with the problem of characters that Python doesn't allow in identifiers. For example, gcc allows "$" in C identifiers (e.g. a field named "egg$"), but Python doesn't allow this character. At least you can use getattr() to access such names. For example:

    >>> s = bytes(range(256)).decode('latin-1')
    >>> T = type('T', (), {s: 0})
    >>> t = T()
    >>> getattr(t, s)
    0