[Python-Dev] pathlib - current status of discussions
Brett Cannon
brett at python.org
Wed Apr 13 15:30:30 EDT 2016
More information about the Python-Dev mailing list
Wed Apr 13 15:30:30 EDT 2016
- Previous message (by thread): [Python-Dev] pathlib - current status of discussions
- Next message (by thread): [Python-Dev] pathlib - current status of discussions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 13 Apr 2016 at 12:25 Chris Angelico <rosuav at gmail.com> wrote: > On Thu, Apr 14, 2016 at 3:10 AM, Brett Cannon <brett at 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() > I'm assuming the C code will do what you're suggesting. My way is just faster to write in 2 minutes of coding. :) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160413/c07829d5/attachment.html>
- Previous message (by thread): [Python-Dev] pathlib - current status of discussions
- Next message (by thread): [Python-Dev] pathlib - current status of discussions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list