(original) (raw)

On Thu, Apr 14, 2016 at 3:10 AM, Brett Cannon <brett@python.org> 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).

All of them have this construct:

try:
path = path.\_\_fspath\_\_()
except AttributeError:
pass

Is that the intention, or should the exception catching be narrower? I
know it's clunky to write it in Python, but AIUI it's less so in C:

try:
callme = path.\_\_fspath\_\_
except AttributeError:
pass
else:
path = callme()