io.FileIO is binary I/O, ans actually optional. Default file type is
io.TextIOWrapper, which provides str results. CPython3 explicitly describes
io.TextIOWrapper as buffered I/O, but we don't have buffering support yet
anyway.

Now schedule is: for native types, we call ->make_new() C-level method, which
should perform actions of __new__ and __init__ (note that this is not
compliant, but is efficient), but for user types, __new__ and __init__ are
called as expected.

Also, make sure we convert scalar attribute value to a bound-pair tight in
mp_obj_class_lookup() method, which avoids converting it again and again in
its callers.

Signed-off-by: Sven Wegener <sven.wegener@stealer.net>

This time, in mp_seq_cmp_bytes(). How many more cases are still lurking?

Done in generalized manner, allowing any stream class to be specified as
working with bytes.

sep=None is TODO.

This should now have correct (and optimal) behaviour.

Addresses issue #610.

Debugging output for emit_glue now simplified so that the init and
deinit functions are no longer needed.

__debug__ now resolves to True or False.  Its value needs to be set by
mp_set_debug().

TODO: call mp_set_debug in unix/ port.

TODO: optimise away "if False:" statements in compiler.

Infra for counts of other types is there, need last mile to be implemented.

Having both MP_OBJ_NOT_SUPPORTED and MP_OBJ_NULL is arguably confusing.

This is better than forcing each getiter() implementation to raise exception.

Updated functions now do proper checking that n_kw==0, and are simpler
because they don't have to explicitly raise an exception.  Down side is
that the error messages no longer include the function name, but that's
acceptable.

Saves order 300 text bytes on x64 and ARM.

Likely there are other functions that should be renamed, but this is a
start.

For consistency with MICROPY_MOD_SYS_STDFILES, etc.

This is not fully correct re: error handling, because we should check that
that types are used consistently (only str's or only bytes), but magically
makes lot of functions support bytes.

Two things are handled here: allow to compare native subtypes of tuple,
e.g. namedtuple (TODO: should compare type too, currently compared
duck-typedly by content). Secondly, allow user sunclasses of tuples
(and its subtypes) be compared either. "Magic" I did previously in
objtype.c covers only one argument (lhs is many), so we're in trouble
when lhs is native type - there's no other option besides handling
rhs in special manner. Fortunately, this patch outlines approach with
fast path for native types.

This was hit when trying to make urlparse.py from stdlib run. Took
quite some time to debug.

TODO: Reconsile bound method creation process better, maybe callable is
to generic type to bind at all?

Similar to closure and cell.