[Python-Dev] pathlib - current status of discussions
ethan at stoneleaf.us
Wed Apr 13 13:49:48 EDT 2016
On 04/13/2016 10:22 AM, Alexander Walters wrote:
> On 4/13/2016 13:10, Brett Cannon wrote:
>> 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.
More information about the Python-Dev