Barry Warsaw barry at python.org
Wed Apr 6 15:43:34 EDT 2016

• Previous message (by thread): [Python-Dev] When should pathlib stop being provisional?
• Next message (by thread): [Python-Dev] When should pathlib stop being provisional?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Apr 06, 2016, at 12:44 PM, Nick Coghlan wrote:

>The next challenge would then be to make a list of APIs to be updated
>for 3.6 to implicitly accept "rich path" objects via the agreed
>convention, with pathlib.PurePath used as a test class:
>
>* open()
>* codecs.open() (et al)
>* io.*
>* os.path.*
>* other os functions
>* shutil.*
>* tempfile.*
>* shelve.*
>* csv.*

Aside from the name of the attribute (though I'm partial to __path__), I think
this would go a long way toward making path objects nicer to work with.  And
right, it doesn't have to be 100% but this would be a big improvement.

Cheers,
-Barry

---

• Previous message (by thread): [Python-Dev] When should pathlib stop being provisional?
• Next message (by thread): [Python-Dev] When should pathlib stop being provisional?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list