On 04/13/2016 10:22 AM, Alexander Walters wrote:
On 4/13/2016 13:10, Brett Cannon wrote:
https://gist.github.com/brettcannon/b3719f54715787d54a206bc011869aa1
has the four potential approaches implemented (although it doesn't
follow the "separate functions" approach some are proposing and
instead goes with the allow_bytes approach I originally proposed).
Number 4 is my personal favorite - it has a simple control flow path and
is the least needlessly restrictive.
Number 3: it allows bytes, but only when told it's okay to do so.
Having code get a bytes object when one is not expected is not a
headache we need to inflict on anyone.
--
~Ethan~
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
